Methods for internet communication security

ABSTRACT

The present disclosure relates to network security software cooperatively configured on plural nodes to authenticate and authorize devices, applications, users, and data protocol in network communications by exchanging nonpublic identification codes, application identifiers, and data type identifiers via pre-established communication pathways and comparing against pre-established values to provide authorized communication and prevent compromised nodes from spreading malware to other nodes.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part of U.S. application Ser. No. 15/949,749, filed Apr. 10, 2018, and this application further claims the benefit of priority from U.S. Provisional Application No. 62/731,529, filed Sep. 14, 2018, U.S. Provisional Application No. 62/655,633, filed Apr. 10, 2018, U.S. Provisional Application No. 62/609,252, filed Dec. 21, 2017, U.S. Provisional Application No. 62/609,152, filed Dec. 21, 2017, and U.S. Provisional Application No. 62/569,300, filed Oct. 6, 2017. All of the foregoing related applications (hereinafter referred to as the “REFERENCE APPLICATIONS”), in their entirety, are incorporated herein by reference.

FIELD OF THE INVENTION

The present disclosure relates to systems, methods, and apparatuses to secure computer networks associated with distributed ledgers and their application against network-borne security threats.

BACKGROUND OF THE INVENTION

Distributed ledger technology includes a peer-to-peer network which timestamps records by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. While such technologies are effective at creating immutable records, the surrounding ecosystems have proven vulnerable to network-based attack, including ecosystems for most of the large cryptocurrency exchanges (including ICO's). In the past, stolen private keys have been transmitted to a remote location and used to author digital signatures on illicit transactions, causing transfer of ownership of billions of dollars' worth of cryptocurrency assets to anonymous third parties. Once private account keys are exfiltrated, current distributed ledger technology may be powerless to prevent nefarious transactions. In fact, due to immutability, as a practical matter it may be difficult or impossible to undo transactions.

Ecosystem participants must also be concerned about risks created by third party software that builds on distributed ledger technology designed to provide added functionality (e.g., payment processors, wallets, fintech applications, smart contract platforms). Malware may exploit code defects in these application, for example to exfiltrate private account keys or spoof legitimate processes.

Distributed ledgers could also be subject to denial of service-like attacks in which bad actors flood the ecosystem with a large number of transactions containing bogus data, particularly in a distributed ledger configured to accept large quantities of data from a low-trust or trustless ecosystem (i.e., an ecosystem where users require little or no authorization to contribute data to the database), or in an ecosystem with compromised private keys. Depending on the algorithm used to validate blocks, communication among peers could be significantly slowed and the functionally hobbled.

Perhaps most significantly, hackers in control of ecosystem nodes and/or private keys can potentially inject malware into a distributed ledger ecosystem via smart contracts. Smart contracts are computer code uploaded to digitally facilitate, verify, or enforce the negotiation or performance of a contract. Bogus smart contracts could be used to force users to malware functions, for example involuntarily committing parties to transfer assets, exfiltrating or corrupting data, or ransoming user's access to their assets or data (a ransomware smart contract). Recently, for example, someone injected malicious code into a cryptocurrency trading platform via a smart contract, enabling the attacker to read private keys belonging to users' wallets.

The foregoing examples map out the vulnerabilities in distributed ledger technology and highlight the fact that as this technology continues to be widely adopted an extensive attack surface is presented. This surface exists because distributed ledger technology, to date, lacks intrinsic network security. Though designed to be deployed across networks (including the public Internet), distributed ledger security features are focused on protecting its logical functionality, specifically (1) guaranteeing that pre-existing records in a distributed ledger have not been altered; and (2) requiring that all additions to the distributed ledger are digitally signed using private keys created by owners or authorized users of the added information. Moreover, despite meticulously and immutably recording the relationships between records, distributed ledger protocols do not require encoding of an audit trail to determine the source of records—ideally they would accurately and consistently identify which device, software, or user/owner posted a transaction for addition to a distributed ledger. This gap further limits the ability to detect and mitigate network-based attacks.

BRIEF SUMMARY OF THE INVENTION

Certain embodiments may provide, for example, a product for authenticating and authorizing provenance of information for one or more information management processes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) receiving a network packet via the communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process; and iv) passing the information to one or more information management processes.

A. In certain embodiments, for example, the authorizing communication may further comprise: a) sending the local program identification code to the computing device via the communication pathway; b) receiving, in response to the sending, a remote application identification code for a remote application program; and c) comparing the remote application identification code with a pre-established value for the remote application program. In certain embodiments, for example, the further communication management operations may comprise: a) sending a data model identification code for the communication pathway to the computing device via the communication pathway; b) receiving, in response to the sending, the data model identification code from the computing device; and c) comparing the received data model identification code with a pre-established value for the communication pathway.

B. In certain embodiments, for example, the communication management operations may further comprise: translating the information to a format expected by the information management process. In certain embodiments, for example, the information may be translated from a pre-established format, the pre-established format determined from a data model identification code for the communication pathway.

C. In certain embodiments, for example, the communication pathway may be encrypted by series of single-use rotated cryptographic keys.

D. In certain embodiments, for example, at least a portion of the communication management operations may be configured to be performed in a processor-accessible kernel space. In certain embodiments, for example, at least a portion of the communication management operations may be configured to be performed in a processor-accessible application space.

E. In certain embodiments, for example, the communication pathway may have a one-to-one correspondence to an n-tuple (as referred to herein, an n-tuple may be, for example, an at least a 2-tuple, an at least a 3-tuple, an at least a 5-tuple, an at least a 6-tuple, an at least an 8-tuple, an at least a 10-tuple, or an at least a 12-tuple) comprising the local program identification code, the destination port number, and a data model identification code.

F. In certain embodiments, for example, the communication management operations may comprise: confirming that the computing device has consulted a pre-specified local policy to specifically authorize network packet communication via the communication pathway.

G. In certain embodiments, for example, the communication management operations may further comprise: confirming the information conforms to a data model pre-assigned to the communication pathway. In certain embodiments, for example, the communication management operations may further comprise: confirming the information conforms to a data range pre-assigned to the communication pathway. In certain embodiments, for example, the communication management operations may further comprise: confirming the information conforms to a command type pre-assigned to the communication pathway.

H. In certain embodiments, for example, the information may comprise at least a portion of an executable code. In certain embodiments, for example, the information may comprise at least a portion of a script. In certain embodiments, for example, the information may comprise at least a portion of a transaction. In certain embodiments, for example, the transaction may be configured to modify ownership of at least one token. In certain embodiments, for example, the transaction may be configured to create a smart contract. In certain embodiments, for example, the transaction may be configured to invoke a smart contract method. In certain embodiments, for example, the transaction may be configured to encode data in a file. In certain embodiments, for example, the information may comprise at least a portion of a proposed block of transactions. In certain embodiments, for example, the information may comprise at least a portion of a protocol message.

I. In certain embodiments, for example, the one or more information management processes may comprise a distributed ledger management process. In certain embodiments, for example, the one or more information management processes may comprise a supply chain management process. In certain embodiments, for example, the one or more information management processes may comprise a fintech service. In certain embodiments, for example, the one or more information management processes may comprise a transaction processing service. In certain embodiments, for example, the one or more information management processes may comprise a file update process.

J. In certain embodiments, for example, the one or more information management processes may be distributed on a peer-to-peer network.

K. In certain embodiments, for example, the remote application program may be a wallet on the computing device. In certain embodiments, for example, the computing device may be a mobile device.

Certain embodiments may provide, for example, a product for authenticating and authorizing provenance of information for one or more information management processes. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable on a processor to perform communication management operations (for example for information management processes). In certain embodiments, for example, the communication management operations may comprise authorizing communication with a computing device on a network. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise sending a nonpublic first identification code via a communication pathway (for example a TCP or a UDP communication pathway), the communication pathway pre-established on the network. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise receiving, after sending the nonpublic first identification code (and/or in response to the sent nonpublic first identification code), a nonpublic computing device identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network. In certain embodiments, for example, the communication management operations may comprise receiving (or the communication management operations may be configured to receive) a network packet comprising (a) information and (b) an encrypted parameter via the pre-established communication pathway. In certain embodiments, for example, the communication management operations may comprise verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process. In certain embodiments, for example, the communication management operations may comprise passing the information to one or more information management processes.

A. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising a block or a portion of a block, the block configured to be appended to a blockchain. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising source code. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a smart contract. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of an executable code. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a script.

B. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a transaction. In certain embodiments, for example, the transaction may be configured to modify ownership of at least one token. In certain embodiments, for example, the transaction may be configured to create a smart contract. In certain embodiments, for example, the transaction may be configured to invoke a smart contract method. In certain embodiments, for example, the transaction may be configured to encode data in a file. In certain embodiments, for example, the transaction may be requested by a requestor, wherein authenticating and authorizing provenance comprise: establishing a trust relationship (for example mutual authentication and authorization) with the requestor and separately with a node hosting the requestor. In certain embodiments, for example, the requestor may comprise a user-process. In certain embodiments, for example, the requestor may comprise an executing (for example a self-executing) computer program and/or smart contract.

C. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a proposed block of transactions. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of gossip. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a protocol message. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a consensus protocol message. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a consensus vote. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a memory pool. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a memory pool snapshot. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a committed block. In certain embodiments, for example, the communication management operations may be configured to process information, the information comprising at least a portion of a distributed ledger.

D. In certain embodiments, for example, the communication management operations may further comprise: inspecting the information, the encrypted parameter, and/or a decrypted form of the parameter to verify compliance with a distributed ledger messaging protocol.

E. In certain embodiments, for example, the one or more information management processes may comprise a file update process. In certain embodiments, for example, the one or more information management processes may comprise a database management system process. In certain embodiments, for example, the one or more information management processes may comprise a distributed ledger management system. In certain embodiments, for example, the one or more information management processes may comprise a cryptographic service. In certain embodiments, for example, the one or more information management processes may comprise a peer membership service. In certain embodiments, for example, the one or more information management processes may comprise a trust service. In certain embodiments, for example, the one or more information management processes may comprise a transaction processing service. In certain embodiments, for example, the one or more information management processes may comprise a smart contract processing service. In certain embodiments, for example, the one or more information management processes may comprise a smart contract endorsement service. In certain embodiments, for example, the one or more information management processes may comprise an ordering service. In certain embodiments, for example, the one or more information management processes may comprise a memory pool management service. In certain embodiments, for example, the one or more information management processes may comprise a blockchain block management service. In certain embodiments, for example, the one or more information management processes may comprise a supply chain process. In certain embodiments, for example, the one or more information management processes may comprise a fintech service. In certain embodiments, for example, the one or more information management processes may comprise a programmable ledger process. In certain embodiments, for example, the one or more information management processes may comprise a hyperledger fabric process. In certain embodiments, for example, the one or more information management processes may comprise a distributed ledger or a portion of a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a memory pool of unconfirmed transactions for a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a key index history of a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a transaction log for a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a state database for a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a block index for a distributed ledger. In certain embodiments, for example, the one or more information management processes may comprise a blockchain.

F. In certain embodiments, for example, the one or more information management processes may encode at least a portion of the information in a distributed ledger.

G. In certain embodiments, for example, the one or more information management processes may endorse transactions. In certain embodiments, for example, the one or more information management processes may verify and/or validate transaction results. In certain embodiments, for example, the one or more information management processes may verify endorsements. In certain embodiments, for example, the one or more information management processes may read information from a file (for example a distributed ledger). In certain embodiments, for example, the one or more information management processes may write information to a file (for example a distributed ledger). In certain embodiments, for example, the one or more information management processes may write a smart contract to a distributed ledger. In certain embodiments, for example, the one or more information management processes may add a block to a blockchain. In certain embodiments, for example, the one or more information management processes may query a database (for example a distributed ledger).

H. In certain embodiments, for example, the one or more information management processes may process, transmit, and/or store information for a fintech application. In certain embodiments, for example, the one or more information management processes may process, transmit, and/or store information for a payments provider. In certain embodiments, for example, the one or more information management processes may process, transmit, and/or store information for a bank. In certain embodiments, for example, the one or more information management processes may process, transmit, and/or store information for a loan service (for example a payday loan service). In certain embodiments, for example, the one or more information management processes may process, transmit, and/or store information for a peer-to-peer lender (for example a person-to-person lender, business-to-person, or business-to-business lender).

I. In certain embodiments, for example, the passing may be configured to pass the information to a wallet. In certain embodiments, for example, the passing may be configured to pass the information to a programmable ledger process. In certain embodiments, for example, the passing may be configured to pass the information to a smart contract generation software. In certain embodiments, for example, the passing may be configured to pass the information to a distributed ledger software. In certain embodiments, for example, the passing may be configured to pass the information to a trust engine. In certain embodiments, for example, the passing may be configured to pass the information to an ordering engine. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one member of a peer-to-peer network.

J. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one fintech application. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one payments provider. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one bank. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one loan service. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one peer-to-peer lender. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one law firm. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one police department. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one vehicle registry. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one private cloud (for example a private cloud hosting a private cryptocurrency for securities settlements). In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one voting system. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one supply chain system, In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one video stream (for example on-demand video stream).

K. In certain embodiments, for example, the communication management operations may be configured to protect at least one member of a peer-to-peer network from malicious smart contracts and/or malicious transactions.

L. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one member of a private overlay network. In certain embodiments, for example, the private overlay network may host and/or maintain a private distributed ledger. In certain embodiments, for example, the private overlay network may conform to an Invisible Internet Project (i2p) standard. In certain embodiments, for example, the product may be configured to provide network security for a node performing computations for a private distributed ledger. In certain embodiments, for example, the computing device may perform computations for a private distributed ledger. In certain embodiments, for example, the product may be configured to provide network security for a private distributed ledger. In certain embodiments, for example, the computing device may provide network access to a private distributed ledger.

M. In certain embodiments, for example, the product may be embedded in (or linkable with and/or callable by) an application software. In certain embodiments, for example, the product may be embedded in (or linkable with and/or callable by) a wallet application. In certain embodiments, for example, the product may be embedded in (or linkable with and/or callable by) a distributed ledger fabric.

N. In certain embodiments, for example, the communication management operations may further comprise: passing the parameter with the information to the one or more information management processes. In certain embodiments, for example, the passed parameter may be encrypted. In certain embodiments, for example, the passed parameter may be unencrypted.

O. In certain embodiments, for example, the communication management operations may further comprise: decrypting the encrypted parameter using a decryption scheme independent of any encryption/decryption scheme of the one or more information management processes. In certain embodiments, for example, the authorizing, receiving, and/or verifying may be configured to be transparent to the one or more information management processes (for example to one or more distributed ledger processes). In certain embodiments, for example, the communication management operations may be configured to be transparent to the one or more information management processes (for example to one or more distributed ledger processes).

P. In certain embodiments, for example, the communication management operations may further comprise: comparing the decrypted form of the parameter with an information protocol identifier to confirm that the information conforms to an authorized format.

Q. In certain embodiments, for example, the product may be configured to run on a virtual machine. In certain embodiments, for example, the product may be configured to run in a hypervisor. In certain embodiments, for example, the product may be configured to be shared by multiple containers. In certain embodiments, for example, the computing device may be a virtual machine.

R. In certain embodiments, for example, the communication management operations may further comprise: obtaining the nonpublic computing device identification code from a network packet (a higher-than-OSI layer three portion of the network packet).

S. In certain embodiments, for example, the comparing the computing device identification code may be initiated in a kernel space of the first computing device.

T. In certain embodiments, for example, the communication management operations may further comprise: reading the preconfigured value for the computing device from a configuration file resident on a node hosting the processor.

U. In certain embodiments, for example, the nonpublic first identification code and nonpublic computing device identification code may be shared secrets between the computing device and a node hosting the processor.

V. In certain embodiments, for example, the communication management operations may further comprise: encrypting the nonpublic first identification code for the sending.

W. In certain embodiments, for example, the communication management operations may be configured to decrypt the received nonpublic computing device identification code. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic computing device identification code with a first single-use cryptographic key.

X. In certain embodiments, for example, the communication management operations may be configured to process wildcard characters present in the computing device identification code and/or the nonpublic first identification code.

Y. In certain embodiments, for example, the communication management operations may further comprise: separately authorizing communication with the process. In certain embodiments, for example, the separately authorizing may be performed before the receiving. In certain embodiments, for example, the separately authorizing may comprise sending a nonpublic second identification code to the computing device via the pre-established communication pathway. In certain embodiments, for example, the separately authorizing may comprise receiving, after sending the nonpublic second identification code (for example in response to the sent nonpublic second identification code), a nonpublic process identification code via the pre-established communication pathway. In certain embodiments, for example, the separately authorizing may comprise comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product. In certain embodiments, for example, the separately authorizing may comprise: a) sending a nonpublic second identification code to the computing device via the pre-established communication pathway; b) receiving, after sending the nonpublic second identification code (for example in response to the sent nonpublic second identification code), a nonpublic process identification code via the pre-established communication pathway; and c) comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product. In certain embodiments, for example, the communication management operations may further comprise: encrypting the nonpublic second identification code for sending. In certain embodiments, for example, the communication management operations may be configured to decrypt the received nonpublic process identification code. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic process identification code with a second single-use cryptographic key. In certain embodiments, for example, the communication management operations may further comprise: further authorizing an information protocol of the information. In certain embodiments, for example, the further authorizing may be performed before the receiving a network packet.

Z. In certain embodiments, for example, the further authorizing may comprise sending a nonpublic third identification code to the computing device via the pre-established communication pathway. In certain embodiments, for example, the further authorizing may comprise receiving, after sending the nonpublic third identification code (for example in response to the sent third nonpublic identification code), a nonpublic information protocol identification code via the pre-established communication pathway. In certain embodiments, for example, the further authorizing may comprise comparing the nonpublic information protocol identification code with a preconfigured value for the pre-established communication pathway, to confirm that the information protocol is authorized for the pre-established communication pathway. In certain embodiments, for example, the further authorizing may comprise: a) sending a nonpublic third identification code to the computing device via the pre-established communication pathway; b) receiving, after sending the nonpublic third identification code (for example in response to the sent third nonpublic identification code), a nonpublic information protocol identification code via the pre-established communication pathway; and c) comparing the nonpublic information protocol identification code with a preconfigured value for the pre-established communication pathway, to confirm that the information protocol is authorized for the pre-established communication pathway. In certain embodiments, for example, the communication management operations may be configured to send the nonpublic second identification code and the nonpublic third identification code in a single network packet. In certain embodiments, for example, the separately authorizing and/or further authorizing may be performed prior to the receiving a network packet. In certain embodiments, for example, the communication management operations may further comprise: encrypting the nonpublic third identification code for sending. In certain embodiments, for example, the communication management operations may be configured to decrypt the received nonpublic information protocol identification code. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic information protocol identification code with a third single-use cryptographic key. In certain embodiments, for example, the third single-use cryptographic key may be the same as the second single-use cryptographic key. In certain embodiments, for example, the separately authorizing and/or the further authorizing may be performed prior to the receiving a network packet and/or prior to any communication of application data between via the pre-established communication pathway. In certain embodiments, for example, the communication management operations may further comprise: inspecting the nonpublic third identification code and/or the nonpublic information protocol identification code to identify an exclusive list of instructions authorized to be contained in the information. In certain embodiments, for example, the communication management operations may further comprise: inspecting the nonpublic third identification code and/or the nonpublic information protocol identification code to identify a list of prohibited instructions, the list of prohibited instructions not authorized to be executed based on instructions contained in the information.

AA. In certain embodiments, for example, the communication management operations may further comprise receiving a data packet from a first port assigned to one of the one or more information management processes, the data packet comprising a payload and a second port number. In certain embodiments, for example, the communication management operations may further comprise assembling a packet segment for the received data packet, the packet segment comprising the payload, a nonpublic identifier for the one of the one or more information management processes, and a data type identifier. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a data packet from a first port assigned to one of the one or more information management processes, the data packet comprising a payload and a second port number; and ii) assembling a packet segment for the received data packet, the packet segment comprising the payload, a nonpublic identifier for the one of the one or more information management processes, and a data type identifier. In certain embodiments, for example, the communication management operations may further comprise: configuring the pre-established communication pathway to have a one-to-one correspondence to an n-tuple comprising the nonpublic identifier for the one of the one or more information management processes, a nonpublic destination application identifier, the second port number, and the data type identifier. In certain embodiments, for example, each of a series of network packet communications of user-application data between the first port and a second port comprise: transmission of a network packet to a third port, the third port assigned to network security software resident on the computing device, the third port having a one-to-one correspondence with the second port number, the second port number assigned to the second port, the second port assigned to a user-application, the network packet comprising the first application identifier and the data type identifier. In certain embodiments, for example, the communication management operations may further comprise: encrypting the nonpublic identifier for the one of the one or more information management processes and the data type identifier by one of a series of single-use encryption keys in the each of the series of network packet communications. In certain embodiments, for example, all communications of user-application data between the first port and the second port comprise the series of network packet communications. In certain embodiments, for example, the communication management operations may further comprise: inspecting the data type identifier to identify an exclusive list of instructions authorized to be contained in the information. In certain embodiments, for example, the communication management operations may further comprise: inspecting the data type identifier to identify a list of prohibited instructions, the list of prohibited instructions not authorized to be executed based on instructions contained in the information.

AB. In certain embodiments, for example, the communication management operations may further comprise intercepting a network connection request from a first port assigned to one of the one or more information management processes, the request comprising a second port number. In certain embodiments, for example, the communication management operations may further comprise verifying that the one of the one or more information management processes is specifically authorized to communicate with a second port, the second port number assigned to the second port (for example, verifying comprising comparing a port number assigned to the first port with a list of allowed process identifiers and allowed second port numbers). In certain embodiments, for example, the communication management operations may further comprise: i) intercepting a network connection request from a first port assigned to one of the one or more information management processes, the request comprising a second port number; and ii) verifying that the one of the one or more information management processes is specifically authorized to communicate with a second port, the second port number assigned to the second port. In certain embodiments, for example, the verifying that the one of the one or more information management processes is specifically authorized to communicate with a second port may be performed prior to forming the pre-established communication pathway.

AC. In certain embodiments, for example, the communication management operations may further comprise forming the pre-established communication pathway, comprising intercepting a network connection request from a second port, the second port hosted by the computing device, the request comprising a first port number. In certain embodiments, for example, the communication management operations may further comprise verifying that a first port is specifically authorized to receive packet data from the second port, the first port number assigned to the first port. In certain embodiments, for example, the communication management operations may further comprise: forming the pre-established communication pathway, comprising: i) intercepting a network connection request from a second port, the second port hosted by the computing device, the request comprising a first port number; and ii) verifying that a first port is specifically authorized to receive packet data from the second port, the first port number assigned to the first port. In certain embodiments, for example, the communication management operations may further comprise: confirming that the computing device has consulted a pre-specified local policy to specifically authorize network packet communication between the first port and the second port. In certain embodiments, for example, the communication management operations may further comprise: receiving an encrypted identifier for the pre-specified local policy from the computing device. In certain embodiments, for example, the communication management operations may be configured to process a pre-specified local policy comprising a record, the record comprising an identifier for one of the one or more information management processes, the second application identifier, a data type identifier, and the first port number. In certain embodiments, for example, the communication management operations may be configured to process a pre-specified local policy further comprising a flag, the flag specifying whether the pre-established communication pathway may be unidirectional or bidirectional. In certain embodiments, for example, the intercepting may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the communication management operations may further comprise receiving a network packet via the communication pathway, the network packet comprising the first port number, information, an identifier for a process sending the information, and the an information type identifier. In certain embodiments, for example, the communication management operations may further comprise comparing the identifier for the sending process and the information type identifier with pre-established values, the pre-established values identified based on the first port number. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a network packet via the communication pathway, the network packet comprising the first port number, information, an identifier for a process sending the information, and the an information type identifier; and ii) comparing the identifier for the sending process and the information type identifier with pre-established values, the pre-established values identified based on the first port number. In certain embodiments, for example, the communication management operations may be configured to locate the identifier for the sending process and the information type identifier in higher-than-OSI layer three portions of the network packet. In certain embodiments, for example, the comparing the identifier for the sending process may be initiated in a kernel of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: translating the information to a format expected by one of the one or more information management processes. In certain embodiments, for example, the communication management operations may further comprise: translating the information from the sending process from a pre-established format, the pre-established format determined from the information type identifier.

AD. In certain embodiments, for example, a portion of the communication management operations may be configured for execution in a kernel space, and a further portion of the communication management operations may be configured for execution in an application space.

Certain embodiments may provide, for example, a method for authenticating and authorizing provenance of information for one or more information management processes. In certain embodiments, for example, the method may comprise authorizing communication with a computing device on a network. In certain embodiments, for example, the authorizing communication may comprise sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network. In certain embodiments, for example, the authorizing communication may comprise receiving, in response to the sent nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network. In certain embodiments, for example, the method may comprise receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter. In certain embodiments, for example, the method may comprise verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process. In certain embodiments, for example, the method may comprise passing the information to the one or more information management processes.

A. In certain embodiments, for example, the received information in the network packet may be sent to a wallet. In certain embodiments, for example, the received information in the network packet may be sent to a programmable ledger process. In certain embodiments, for example, the received information in the network packet may be sent to a smart contract generation software. In certain embodiments, for example, the received information in the network packet may be sent to a distributed ledger software. In certain embodiments, for example, the received information in the network packet may be sent to a trust engine. In certain embodiments, for example, the received information in the network packet may be sent to an ordering engine.

B. In certain embodiments, for example, one or more of the foregoing wallet, ledger process, softwares, or engines may be running on the computing device. In certain embodiments, for example, the computing device may encode at least a portion of the information in a distributed ledger. In certain embodiments, for example, the computing device may host a file update process. In certain embodiments, for example, the computing device may host a database management system process. In certain embodiments, for example, the computing device may host a distributed ledger management system. In certain embodiments, for example, the computing device may host a cryptographic service. In certain embodiments, for example, the computing device may host a peer membership service. In certain embodiments, for example, the computing device may host a trust service. In certain embodiments, for example, the computing device may host a transaction processing service. In certain embodiments, for example, the computing device may host a smart contract processing service. In certain embodiments, for example, the computing device may host a smart contract endorsement service. In certain embodiments, for example, the computing device may host an ordering service. In certain embodiments, for example, the computing device may host a memory pool management service. In certain embodiments, for example, the computing device may host a blockchain block management service. In certain embodiments, for example, the computing device may host a supply chain process. In certain embodiments, for example, the computing device may host a fintech service. In certain embodiments, for example, the computing device may host a programmable ledger process. In certain embodiments, for example, the computing device may host a hyperledger fabric process. In certain embodiments, for example, the computing device may host a distributed ledger or a portion of a distributed ledger. In certain embodiments, for example, the computing device may host a memory pool of unconfirmed transactions for a distributed ledger. In certain embodiments, for example, the computing device may host a key index history of a distributed ledger. In certain embodiments, for example, the computing device may host a transaction log for a distributed ledger. In certain embodiments, for example, the computing device may host a state database for a distributed ledger. In certain embodiments, for example, the computing device may host a block index for a distributed ledger. In certain embodiments, for example, the computing device may host a blockchain. In certain embodiments, for example, the computing device may host more than one of the above, for instance, several, most, substantially all, all, portions of some, portions of all, and/or hybrids of some or all of the above.

C. In certain embodiments, for example, the computing device may endorse transactions. In certain embodiments, for example, the computing device may verify and/or validates transaction results. In certain embodiments, for example, the computing device may verify endorsements. In certain embodiments, for example, the computing device may read information from a file (for example a distributed ledger). In certain embodiments, for example, the computing device may write information to a file (for example a distributed ledger). In certain embodiments, for example, the computing device may write a smart contract to a distributed ledger. In certain embodiments, for example, the computing device may add a block to a blockchain. In certain embodiments, for example, the computing device may query a database (for example a distributed ledger). In certain embodiments, for example, the computing device may perform more than one of the above functions, for instance, several, most, substantially all, all, portions of some, portions of all, and/or hybrids of some or all of the above functions.

D. In certain embodiments, for example, the computing device may be a member of a peer-to-peer network. In certain embodiments, for example, the computing device may be mobile. In certain embodiments, for example, the computing device may protect at least one member of a peer-to-peer network from malicious smart contracts and/or malicious.

E. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one fintech application. In certain embodiments, for example, the computing device may provide network security for at least one payments provider. In certain embodiments, for example, the computing device may provide network security for at least one bank. In certain embodiments, for example, the computing device may provide network security for at least one loan service. In certain embodiments, for example, the computing device may provide network security for at least one peer-to-peer lender. In certain embodiments, for example, the computing device may provide network security for at least one law firm. In certain embodiments, for example, the computing device may provide network security for at least one police department. In certain embodiments, for example, the computing device may provide network security for at least one vehicle registry. In certain embodiments, for example, the computing device may provide network security for at least one private cloud (for example a private cloud hosting a private cryptocurrency for securities settlements). In certain embodiments, for example, the computing device may provide network security for at least one voting system. In certain embodiments, for example, the computing device may provide network security for at least one supply chain system, In certain embodiments, for example, the computing device may provide network security for at least one video stream (for example on-demand video stream). In certain embodiments, for example, the computing device may provide network security for more than one of the above entities and/or applications, for instance, several, most, substantially all, all, portions of some, portions of all, and/or hybrids of some or all of the above entities and/or applications.

F. In certain embodiments, for example, the communication management operations may be configured to provide network security for (for example provide secure access to) at least one fintech application. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one payments provider. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one bank. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one loan service. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one peer-to-peer lender. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one law firm. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one police department. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one vehicle registry. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one private cloud (for example a private cloud hosting a private cryptocurrency for securities settlements). In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one voting system. In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one supply chain system, In certain embodiments, for example, the computing device may process, transmit, and/or store information for at least one video stream (for example on-demand video stream). In certain embodiments, for example, the computing device may process, transmit, and/or store information for more than one of the above entities, systems, and/or processes, for instance, several, most, substantially all, all, portions of some, portions of all, and/or hybrids of some or all of the above entities, systems, and/or processes.

G. In certain embodiments, for example, the computing device may provide network security for (for example provide secure access to) at least one member of a private overlay network. In certain embodiments, for example, the private overlay network may host and/or maintain a private distributed ledger. In certain embodiments, for example, the private overlay network may conform to an Invisible Internet Project (i2p) standard. In certain embodiments, for example, the computing device may provide network security for a node performing computations for a private distributed ledger. In certain embodiments, for example, the computing device may perform computations for a private distributed ledger. In certain embodiments, for example, the product may be configured to provide network security for a private distributed ledger. In certain embodiments, for example, the computing device may provide network access to a private distributed ledger.

H. In certain embodiments, for example, the method may comprise any of the communication management operations disclosed herein.

I. In certain embodiments, for example, the method may be performed on a virtual machine. In certain embodiments, for example, the method may be performed on in a hypervisor. In certain embodiments, for example, the method may be performed in containers.

J. In certain embodiments, for example, the network packet may be received from a remote port assigned to network security software running on the computing device. In certain embodiments, for example, the remote port and a local port for the receiving may be both assigned solely in one-to-one relation with the pre-established communication pathway.

K. In certain embodiments, for example, the nonpublic first identification code and nonpublic computing device identification code may be shared secrets between the computing device and one or more nodes performing the method.

Certain embodiments may provide, for example, a method for securely updating a file. In certain embodiments, for example, the method may comprise authorizing communication with a computing device on a network. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise receiving, in response to the sent nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication with a computing device on a network may comprise comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network. In certain embodiments, for example, the method may comprise receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter. In certain embodiments, for example, the method may comprise verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process. In certain embodiments, for example, the method may comprise encoding at least a portion of the information in a file.

A. In certain embodiments, for example, the file may be a distributed file. In certain embodiments, for example, the file may be a database. In certain embodiments, for example, the file may be a distributed ledger (for example a distributed ledger comprising a blockchain). In certain embodiments, for example, the file may be a blockchain. In certain embodiments, for example, the file may be a memory pool. In certain embodiments, for example, the file may be an append-only database.

B. In certain embodiments, for example, the information may comprise a block or a portion of a block, the block configured to be appended to a blockchain.

Certain embodiments may provide, for example, a product for authenticating and authorizing provenance of information for one or more information management processes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic first identification code (and/or in response to the sent nonpublic first identification code), a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process; and iv) passing the information to the one or more information management processes.

Certain embodiments may provide, for example, a method for authenticating and authorizing provenance of information for one or more information management processes, comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, in response to the sent nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process; and iv) passing the information to the one or more information management processes.

Certain embodiments may provide, for example, a method for securely updating a file, comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, in response to the sent nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process; and iv) encoding at least a portion of the information in a file.

Certain embodiments may provide, for example, method to form a secure blockchain, comprising: i) authenticating and authorizing provenance of a network packet, the network packet comprising information; and ii) encoding at least a portion of the information into the secure blockchain.

A. In certain embodiments, for example, the encoding may comprise generating a block incorporating the at least a portion of the information, the block configured to be appended to a blockchain. In certain embodiments, for example, the encoding may further comprise sending the generated block to at least one node on a network. In certain embodiments, for example, the network packet may be received from a node on the network. In certain embodiments, for example, the encoding may comprise passing the information from the kernel space to a blockchain application process.

B. In certain embodiments, for example, the information may comprise at least a portion of a proposed block of transactions. In certain embodiments, for example, the information may comprise at least a portion of gossip. In certain embodiments, for example, the information may comprise at least a portion of a protocol message. In certain embodiments, for example, the information may comprise at least a portion of a consensus protocol message. In certain embodiments, for example, the information may comprise at least a portion of a consensus vote. In certain embodiments, for example, the information may comprise at least a portion of a memory pool. In certain embodiments, for example, the information may comprise at least a portion of a memory pool snapshot. In certain embodiments, for example, the information may comprise at least a portion of a committed block. In certain embodiments, for example, the information may comprise at least a portion of a distributed ledger. In certain embodiments, for example, the information may comprise more than one of the above information types, for instance, several, most, substantially all, all, portions of some, portions of all, and/or hybrids of some or all of the above information types.

C. In certain embodiments, for example, the transaction may be configured to modify ownership of at least one token. In certain embodiments, for example, the transaction may be configured to create a smart contract. In certain embodiments, for example, the transaction may be configured to invoke a smart contract method. In certain embodiments, for example, the transaction may be configured to encode data in a file. In certain embodiments, for example, the transaction may be requested by a requestor, wherein authenticating and authorizing provenance comprise: establishing a trust relationship (for example mutual authentication and authorization) with the requestor and separately with a node hosting the requestor. In certain embodiments, for example, the requestor may comprise a user-process. In certain embodiments, for example, the requestor may comprise an executing (for example a self-executing) computer program and/or smart contract.

D. In certain embodiments, for example, the method may comprise inspecting the information and/or the metadata to verify compliance with a distributed ledger messaging protocol.

E. In certain embodiments, for example, the authenticating and authorizing provenance comprise authorizing a pre-established communication pathway. In certain embodiments, for example, the authorizing the pre-established communication pathway may comprise authorizing one or more of the following: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code via a communication pathway, the communication pathway pre-established on the network; b) receiving, in response to the sent nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) authorizing communication with a remote process, comprising: a) sending a nonpublic second identification code to the computing device via the pre-established communication pathway; b) receiving, in response to the sent nonpublic second identification code, a nonpublic process identification code via the pre-established communication pathway; and c) comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product; and iii) authorizing an information protocol of pre-established communication pathway, comprising: a) sending a nonpublic third identification code to the computing device via the pre-established communication pathway; b) receiving, in response to the sent third nonpublic identification code, a nonpublic information protocol identification code via the pre-established communication pathway; and c) comparing the nonpublic information protocol identification code with a preconfigured value for the pre-established communication pathway, to confirm that the information protocol is authorized for the pre-established communication pathway.

F. In certain embodiments, for example, the authenticating and authorizing provenance comprise: (a) parsing the network packet to obtain metadata, the metadata comprising provenance tracking parameters for the information; and (b) comparing the provenance tracking parameters to predetermined parameters. In certain embodiments, for example, the metadata may be encrypted, the method may further comprise decrypting the metadata. In certain embodiments, for example, the provenance tracking parameters comprising one or more of the following: i) a nonpublic process identification code; and ii) an information protocol identification code.

Certain embodiments may provide, for example, a method to form a secure blockchain, comprising: i) authenticating and authorizing provenance of a network packet received from a first node on a network, the network packet comprising information; ii) generating a block incorporating at least a portion of the information, the block configured to be appended to a blockchain; and iii) sending the generated block to at least a second node on the network.

Certain embodiments may provide, for example, a method to form a secure blockchain, comprising: i) receiving a network packet in a kernel space, the network packet comprising information and metadata; ii) verifying provenance of a network packet, the verifying comprising comparing the metadata to predetermined values; followed by iii) passing the information from the kernel space to a blockchain application process.

Certain embodiments may provide, for example, a product enforcing information protocol security for accessing a distributed ledger. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable on a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise authorizing communication of information according to a first information protocol for a pre-established communication pathway on a network. In certain embodiments, for example, the authorizing communication of information may comprise sending a nonpublic first identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication of information may comprise receiving, after sending the sent nonpublic first identification code, a nonpublic first information protocol identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication of information may comprise comparing the first information protocol identification code with a preconfigured first value, the preconfigured first value assigned to the pre-established communication pathway. In certain embodiments, for example, the communication management operations may comprise receiving a network packet from a computing device via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter. In certain embodiments, for example, the communication management operations may comprise verifying that the received information conforms to the first information protocol, comprising: comparing a decrypted form of the parameter with the preconfigured first value. In certain embodiments, for example, the communication management operations may comprise passing at least a portion of the information to a network, the network configured to manage a distributed ledger.

A. In certain embodiments, for example, the communication management operations may further comprise: discarding the received network packet if it does not conform to the first information protocol.

B. In certain embodiments, for example, the first information protocol may be a representational state transfer protocol. In certain embodiments, for example, the first information protocol may be an Etherium protocol. In certain embodiments, for example, the first information protocol may be a Bitcoin protocol. In certain embodiments, for example, the first information protocol may be a Hyperledger protocol. In certain embodiments, for example, the first information protocol may be an Openchain protocol. In certain embodiments, for example, the first information protocol may be a Corda DLT Blockchain protocol. In certain embodiments, for example, the first information protocol may be a BigChainDB protocol.

C. In certain embodiments, for example, the at least a portion of the information may be converted according to a second information protocol prior to the passing. In certain embodiments, for example, the second information protocol may be a representational state transfer protocol. In certain embodiments, for example, the second information protocol may be an Etherium protocol. In certain embodiments, for example, the second information protocol may be a Bitcoin protocol. In certain embodiments, for example, the second information protocol may be a Hyperledger protocol. In certain embodiments, for example, the second information protocol may be an Openchain protocol. In certain embodiments, for example, the second information protocol may be a Corda DLT Blockchain protocol. In certain embodiments, for example, the second information protocol may be a BigChainDB protocol.

Certain embodiments may provide, for example, a method for enforcing information protocol security for accessing a distributed ledger. In certain embodiments, for example, the method may comprise authorizing communication of information according to a first information protocol for a pre-established communication pathway on a network. In certain embodiments, for example, the authorizing communication may comprise sending a nonpublic first identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise receiving, in response to the sent nonpublic first identification code, a nonpublic first information protocol identification code from a computing device via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise comparing the first information protocol identification code with a preconfigured first value, the preconfigured first value assigned to the pre-established communication pathway. In certain embodiments, for example, the method may comprise receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter. In certain embodiments, for example, the method may comprise verifying that the received information conforms to the first information protocol, comprising: comparing a decrypted form of the parameter with the preconfigured first value. In certain embodiments, for example, the method may comprise passing at least a portion of the information to a network, the network configured to manage a distributed ledger. In certain embodiments, for example, the computing device may host (and/or the information may be received from) any of the foregoing information management processes. In certain embodiments, for example, the computing device may be a member of any of the foregoing computing devices.

Certain embodiments may provide, for example, a product to prevent transactions from compromised addresses. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable on a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise authorizing communication with a computing device on a network. In certain embodiments, for example, the authorizing communication may comprise sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network. In certain embodiments, for example, the authorizing communication may comprise receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise comparing the nonpublic second identification code with a preconfigured value for the computing device. In certain embodiments, for example, the communication management operations may comprise receiving a network packet, the network packet containing (a) information, and (b) a digital signature referencing a public address. In certain embodiments, for example, the communication management operations may comprise detecting a violation of a distributed ledger policy by a peer, the public address assigned to the peer. In certain embodiments, for example, the communication management operations may comprise revoking authorization to communicate with the computing device.

A. In certain embodiments, for example, the detecting a violation may comprise monitoring a published list of distributed ledger policy violations. In certain embodiments, for example, the published list may be indexed by one or more public addresses. In certain embodiments, for example, the published list may be contained in a distributed file (for example in a distributed ledger). In certain embodiments, for example, the communication management operations may further comprise: updating a published list with the violation. In certain embodiments, for example, the communication management operations may further comprise: updating a published list with the violation indexed by the public address.

B. In certain embodiments, for example, the communication management operations may further comprise: notifying network security software running on a plurality of nodes of the revocation. In certain embodiments, for example, the detecting a violation may trigger the distribution of updated security configuration files to a plurality of nodes.

C. In certain embodiments, for example, the communication management operations may further comprise: separately authorizing communication with a process, the process running on the computing device.

D. In certain embodiments, for example, the revoking may comprise revoking authorization to communicate with the process. In certain embodiments, for example, the revoking authorization may comprise terminating the communication pathway. In certain embodiments, for example, the revoking may comprise adding the nonpublic first identification code to a black list of computing devices disallowed for network communication.

E. In certain embodiments, for example, the violation may comprise an attempt to double spend a token or cryptocurrency. In certain embodiments, for example, the violation may comprise an attempt to perform an unauthorized transaction. In certain embodiments, for example, the violation may comprise an attempt to circumvent a distributed ledger policy.

F. In certain embodiments, for example, the public address may be (or may be derived from) a public key of a public key-private key pair, the private key used to form the digital signature.

G. In certain embodiments, for example, the communication management operations may further comprise dropping all network packets received from the computing device following the revoking.

Certain embodiments may provide, for example, a product for recording verified data provenance in a distributed ledger. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable on a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise authorizing communication with a process. In certain embodiments, for example, the authorizing communication may comprise sending a nonpublic first identification code to the computing device via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise receiving, after sending the nonpublic first identification code (for example in response to the sent nonpublic first identification code), a nonpublic process identification code via the pre-established communication pathway. In certain embodiments, for example, the authorizing communication may comprise comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product. In certain embodiments, for example, the communication management operations may comprise receiving a network packet from the computing device, the network packet comprising: (a) information from the process; and (b) an encrypted parameter. In certain embodiments, for example, the communication management operations may comprise authorizing the provenance of the information, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process. In certain embodiments, for example, the communication management operations may comprise encoding the authorized information and the encrypted parameter into one or more distributed ledgers.

A. In certain embodiments, for example, the nonpublic first identification code may comprise the nonpublic process identification code and a nonpublic protocol code, the nonpublic protocol code identifying a protocol for the information.

B. In certain embodiments, for example, the parameter may comprise the nonpublic process identification code and a nonpublic protocol code, the nonpublic protocol code identifying a protocol for the information.

C. In certain embodiments, for example, the authorized information may be modified by appending the encrypted parameter to the information prior to the encoding.

D. In certain embodiments, for example, the modifying may further comprise appending a hash of a nonpublic identification code for the computing device to the information.

E. In certain embodiments, for example, the encoding may comprise computing a hash of the parameter.

F. In certain embodiments, for example, the communication management operations may further comprise separately authorizing communication with a computing device, the process running on the computing device. In certain embodiments, for example, the separately authorizing may comprise: a) sending a nonpublic second identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic second identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network.

Certain embodiments may provide, for example, a product to extend network security to information at rest. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable on a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise parsing a network packet to obtain encrypted first information and separately encrypted first metadata, the first metadata comprising a public first parameter. In certain embodiments, for example, the communication management operations may comprise authenticating and authorizing provenance of the network packet. In certain embodiments, for example, the communication management operations may comprise decrypting the separately encrypted first metadata to obtain the public first parameter. In certain embodiments, for example, the communication management operations may comprise passing the public first parameter and at least a portion of the encrypted first information to one or more information management processes.

A. In certain embodiments, for example, the communication management operations may further comprise: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the sent nonpublic first identification code (for example in response to the sent nonpublic first identification code), a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; and ii) receiving the network packet via the pre-established communication pathway.

B. In certain embodiments, for example, the authenticating and authorizing provenance of the network packet may comprise obtaining provenance parameters from the first information. In certain embodiments, for example, the provenance parameters may comprise a nonpublic process identification code and a nonpublic information protocol identification code.

C. In certain embodiments, for example, the authenticating and authorizing provenance of the network packet may further comprise comparing a nonpublic process identification code with a first preconfigured value and/or comparing the nonpublic information protocol identification code with a second preconfigured value.

D. In certain embodiments, for example, the passed at least a portion of the encrypted first information may comprise a nonpublic process identification code and a nonpublic information protocol identification code.

E. In certain embodiments, for example, the one or more information management processes may be configured to encode the public first parameter and the at least a portion of the encrypted first information into at least one distributed ledger. In certain embodiments, for example, the encoded at least a portion of the encrypted first information may comprise a nonpublic process identification code and a nonpublic information protocol identification code.

F. In certain embodiments, for example, the communication management operations may further comprise retrieving encrypted second information and a public second parameter from at least one distributed ledger via a communication pathway. In certain embodiments, for example, the communication management operations may comprise obtaining at least one cryptographic parameter assigned to the public second parameter. In certain embodiments, for example, the communication management operations may comprise decrypting the at least a portion of the encrypted first information using the at least one cryptographic parameter and/or using at least one further parameter derived from the at least one cryptographic parameter. In certain embodiments, for example, the second information may comprise a nonpublic process identification code and a nonpublic information protocol identification code.

Certain embodiments may provide, for example, a method to secure information in a file. In certain embodiments, for example, the method may comprise receiving a network packet, the network packet comprising encrypted information and separately encrypted metadata, the metadata comprising a public parameter. In certain embodiments, for example, the method may comprise authenticating and authorizing provenance of the network packet. In certain embodiments, for example, the method may comprise decrypting the separately encrypted metadata to obtain the public parameter. In certain embodiments, for example, the method may comprise transmitting the public parameter and at least a portion of the encrypted information for encoding into at least one distributed ledger.

A. In certain embodiments, for example, the method may further comprise: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the sent nonpublic first identification code (for example in response to the sent nonpublic first identification code), a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; and ii) receiving the network packet via the pre-established communication pathway.

B. In certain embodiments, for example, each of the encrypted information and separately encrypted metadata may be encrypted by an indexed cryptographic key. In certain embodiments, for example, the metadata may comprise an index for the indexed cryptographic key. In certain embodiments, for example, the public parameter may be a public key of a public key-private key pair, the public key-private key pair having a private key used to generate the indexed cryptographic key.

C. In certain embodiments, for example, the encoded at least a portion of the encrypted information may be encrypted at rest in the distributed ledger.

D. Certain embodiments may provide, for example, a method of retrieving the at least a portion of the encrypted information. In certain embodiments, for example, the method may comprise retrieving the at least a portion of the encrypted information and the public parameter from the at least one distributed ledger via a communication pathway. In certain embodiments, for example, the method may comprise obtaining at least one cryptographic parameter assigned to the public parameter. In certain embodiments, for example, the method may comprise decrypting the at least a portion of the encrypted information using the at least one cryptographic parameter and/or using at least one further parameter derived from the at least one cryptographic parameter.

E. In certain embodiments, for example, the retrieving may comprise authenticating and authorizing provenance of the network packet. In certain embodiments, for example, the authenticating and authorizing provenance of the retrieved network packet may comprise obtaining provenance parameters from the information, the provenance parameters comprising a nonpublic process identification code and a nonpublic information protocol identification code. In certain embodiments, for example, the authenticating and authorizing provenance of the retrieved network packet may further comprise comparing a nonpublic process identification code with a first preconfigured value and/or comparing the nonpublic information protocol identification code with a second preconfigured value.

Certain embodiments may provide, for example, a product to verify data provenance, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a computing device, comprising: a) sending a nonpublic first identification code to the computing device via a pre-established communication pathway; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the nonpublic second identification code with a preconfigured value for the intermediary computing device; ii) separately authorizing communication with a process, the process running on the computing device; iii) receiving a network packet, the network packet comprising: (a) information; (b) an encrypted first parameter; and (c) an encrypted second parameter; iv) authorizing the network packet, comprising: comparing a decrypted form of the first parameter with a preconfigured identification code for the process; and v) separately authorizing the information, comprising: a) comparing a decrypted form of the second parameter with a preconfigured source identification code to identify a source for the information; and b) verifying that the source for the information is pre-qualified to send data to the computing device.

Certain embodiments may provide, for example, a method to verify data provenance, comprising: i) authorizing communication with an intermediary computing device, comprising: a) sending a nonpublic first identification code to the intermediary computing device via a pre-established communication pathway; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the nonpublic second identification code with a preconfigured value for the intermediary computing device; ii) separately authorizing communication with an intermediary process, the intermediary process running on the intermediary computing device; iii) receiving a network packet, the network packet comprising: (a) information; (b) an encrypted intermediary parameter; and (c) an encrypted source parameter; iv) authorizing the network packet, comprising: comparing a decrypted form of the intermediary parameter with a preconfigured identification code for the intermediary process; and v) separately authorizing the information, comprising: a) comparing a decrypted form of the source parameter with a preconfigured source identification code to identify a source process for the information; and b) verifying that the source process is pre-qualified to send data to the intermediary computing device.

Certain embodiments may provide, for example, a method to remotely verify a security configuration of a peer. In certain embodiments, for example, the method may comprise establishing a security configuration for a first peer and a second peer. In certain embodiments, for example, the establishing a security configuration may comprise immutably encoding a 2-tuple in a distributed ledger, the 2-tuple comprising a first code and a second code. In certain embodiments, for example, the establishing a security configuration may comprise downloading a security configuration file to the first peer, the security configuration file containing a nonpublic first peer identifier and at least one cryptographic primitive. In certain embodiments, for example, the establishing a security configuration may comprise downloading the nonpublic first peer identifier to the second peer. In certain embodiments, for example, the method may comprise negotiating an encrypted communication pathway between the first peer and the second peer, comprising: forming an encryption key at the first peer, the forming comprising: obtaining the at least one cryptographic primitive from the security configuration file. In certain embodiments, for example, the method may comprise computing a first ciphertext parameter at the first peer, comprising: passing the security configuration file through a first one-way function. In certain embodiments, for example, the method may comprise encrypting the first ciphertext parameter at the first peer with the encryption key. In certain embodiments, for example, the method may comprise transmitting a network packet from the first peer to the second peer via the encrypted communication pathway, the network packet containing the encrypted first ciphertext parameter. In certain embodiments, for example, the method may comprise decrypting the encrypted first ciphertext parameter at the second peer. In certain embodiments, for example, the method may comprise computing a second ciphertext parameter at the second peer, comprising: passing a nonpublic first peer identifier through a second one-way function. In certain embodiments, for example, the method may comprise verifying the security configuration of the first peer at the second peer, comprising: obtaining the 2-tuple from the distributed ledger and matching the first ciphertext parameter with the first code and the second ciphertext parameter with the second code. In certain embodiments, for example, computing the second ciphertext parameter may further comprise: further passing a copy of the contents of a predetermined portion of a computer memory through the second one-way function. In certain embodiments, for example, the first one-way function may be a trapdoor function. In certain embodiments, for example, the second one-way function may be a trapdoor function.

Certain embodiments may provide, for example, a product enforcing information protocol security for accessing a distributed ledger, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication of information according to a first information protocol for a pre-established communication pathway on a network, comprising: a) sending a nonpublic first identification code via the pre-established communication pathway; b) receiving, after sending the sent nonpublic first identification code, a nonpublic first information protocol identification code via the pre-established communication pathway; and c) comparing the first information protocol identification code with a preconfigured first value, the preconfigured first value assigned to the pre-established communication pathway; ii) receiving a network packet from a computing device via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information conforms to the first information protocol, comprising: comparing a decrypted form of the parameter with the preconfigured first value; and iv) passing at least a portion of the information to a network, the network configured to manage a distributed ledger.

Certain embodiments may provide, for example, a method for enforcing information protocol security for accessing a distributed ledger, comprising: i) authorizing communication of information according to a first information protocol for a pre-established communication pathway on a network, comprising: a) sending a nonpublic first identification code via the pre-established communication pathway; b) receiving, in response to the sent nonpublic first identification code, a nonpublic first information protocol identification code from a computing device via the pre-established communication pathway; and c) comparing the first information protocol identification code with a preconfigured first value, the preconfigured first value assigned to the pre-established communication pathway; ii) receiving a network packet via the pre-established communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information conforms to the first information protocol, comprising: comparing a decrypted form of the parameter with the preconfigured first value; and iv) passing at least a portion of the information to a network, the network configured to manage a distributed ledger.

Certain embodiments may provide, for example, a product to prevent transactions from compromised addresses, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the nonpublic second identification code with a preconfigured value for the computing device; ii) receiving a network packet, the network packet containing (a) information, and (b) a digital signature referencing a public address; iii) detecting a violation of a distributed ledger policy by a peer, the public address assigned to the peer; followed by iv) revoking authorization to communicate with the computing device.

Certain embodiments may provide, for example, a method to product to prevent transactions from compromised addresses, comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code to the computing device via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the nonpublic second identification code with a preconfigured value for the computing device; ii) receiving a network packet, the network packet containing (a) information, and (b) a digital signature referencing a public address; iii) detecting a violation of a distributed ledger policy by a peer, the public address assigned to the peer; followed by iv) revoking authorization to communicate with the computing device.

Certain embodiments may provide, for example, a product for recording verified data provenance in a distributed ledger, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a process, comprising: a) sending a nonpublic first identification code to the computing device via the pre-established communication pathway; b) receiving, after sending the nonpublic first identification code (for example in response to the sent nonpublic first identification code), a nonpublic process identification code via the pre-established communication pathway; and c) comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product; ii) receiving a network packet from the computing device, the network packet comprising: (a) information from the process; and (b) an encrypted parameter; iii) authorizing the provenance of the information, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process; and iv) encoding the authorized information and the encrypted parameter into one or more distributed ledgers.

Certain embodiments may provide, for example, a product for recording verified data provenance in a distributed ledger, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a process, comprising: a) sending a nonpublic first identification code to the computing device via the pre-established communication pathway; b) receiving, after sending the nonpublic first identification code (for example in response to the sent nonpublic first identification code), a nonpublic process identification code via the pre-established communication pathway; and c) comparing the nonpublic process identification code with a preconfigured value for the process, to confirm that the process is authorized to communicate with the product; ii) receiving a network packet from the computing device, the network packet comprising: (a) information from the process; and (b) an encrypted parameter; iii) authorizing the provenance of the information, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process; and iv) encoding the authorized information and the encrypted parameter into one or more distributed ledgers.

Certain embodiments may provide, for example, a product to extend network security to information at rest, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) parsing a network packet to obtain encrypted first information and separately encrypted first metadata, the first metadata comprising a public first parameter; ii) authenticating and authorizing provenance of the network packet; iii) decrypting the separately encrypted first metadata to obtain the public first parameter; and iv) passing the public first parameter and at least a portion of the encrypted first information to one or more information management processes.

Certain embodiments may provide, for example, a method to secure information in a file, comprising: i) receiving a network packet, the network packet comprising encrypted information and separately encrypted metadata, the metadata comprising a public parameter; ii) authenticating and authorizing provenance of the network packet; iii) decrypting the separately encrypted metadata to obtain the public parameter; and iv) transmitting the public parameter and at least a portion of the encrypted information for encoding into at least one distributed ledger.

Certain embodiments may provide, for example, a method to remotely verify a security configuration of a peer, comprising: i) establishing a security configuration for a first peer and a second peer, comprising: a) immutably encoding a 2-tuple in a distributed ledger, the 2-tuple comprising a first code and a second code; b) downloading a security configuration file to the first peer, the security configuration file containing a nonpublic first peer identifier and at least one cryptographic primitive; and c) downloading the nonpublic first peer identifier to the second peer; ii) negotiating an encrypted communication pathway between the first peer and the second peer, comprising: forming an encryption key at the first peer, the forming comprising: obtaining the at least one cryptographic primitive from the security configuration file; iii) computing a first ciphertext parameter at the first peer, comprising: passing the security configuration file through a first one-way function; iv) encrypting the first ciphertext parameter at the first peer with the encryption key; v) transmitting a network packet from the first peer to the second peer via the encrypted communication pathway, the network packet containing the encrypted first ciphertext parameter; vi) decrypting the encrypted first ciphertext parameter at the second peer; vii) computing a second ciphertext parameter at the second peer, comprising: passing a nonpublic first peer identifier through a second one-way function; and viii) verifying the security configuration of the first peer at the second peer, comprising: obtaining the 2-tuple from the distributed ledger and matching the first ciphertext parameter with the first code and the second ciphertext parameter with the second code.

Certain embodiments may advantageously provide decentralized network security that scales with the state or footprint of a network (for example the footprint of a peer-to-peer network) or application (for example a blockchain application), but instead only depends on the volume of network traffic reaching nodes or computing devices. Certain embodiments, for example, may provide a method to form a secure blockchain, comprising: i) receiving a network packet, the network packet comprising information and metadata; ii) verifying provenance of a network packet, the verifying comprising comparing the metadata to predetermined values; followed by iii) passing the information to a blockchain application process. In certain embodiments, for example, the speed (and/or the operation) of the receiving, verifying, and/or passing may be independent of the state of the blockchain, the number of blocks in the blockchain, the number of computing devices implementing the blockchain, and/or the quantity of data encoded in the blockchain. In certain embodiments, for example, the speed (and/or the operation) of the method may be independent of the state of the blockchain, the number of blocks in the blockchain, the number of computing devices implementing the blockchain, and/or the quantity of data encoded in the blockchain.

Certain embodiments, for example, may provide a method for securing a blockchain, comprising: i) receiving a network packet, the network packet comprising information and metadata; ii) verifying provenance of a network packet, the verifying comprising comparing the metadata to predetermined values; followed by iii) passing the information to a blockchain application process, the speed (and/or the operation) of the method for securing the blockchain independent of the state of the blockchain, the number of blocks in the blockchain, the number of computing devices implementing the blockchain, and/or the quantity of data encoded in the blockchain.

Certain embodiments may advantageously decentralize knowledge regarding authorized connections and cryptographic parameters on a need-to-know basis. For example, in a network of nodes each node may have a configuration file which specifies these parameters only for the connections applicable to the node. Thus there may be no single attack surface or repository for malware to obtain the network configuration information or cryptographic information required to compromise communication between two nodes. A malware attack may have to somehow identify and compromise multiple nodes and then attempt to piece together information required to modify communications between the nodes. Certain embodiments may provide, for example, a method for decentralized management of communications between plural nodes coupled to a network, comprising: i) constructing a series of different local policies representing a global policy for authorized port-to-port communications among the plural nodes; ii) decentralizing the global policy by distributing the series of different local policies among the plural nodes on a need-to-know basis; and ii) restricting port-to-port communications to the authorized port-to-port communications. In certain embodiments, for example, none of the plural nodes may receive the global policy. In certain embodiments, for example, none of the plural nodes may receive a policy that for an authorized port-to-port communication that includes extraneous policy information for communication between other nodes. In certain embodiments, for example, malware may have to independently compromise local policies on multiple nodes to obtain the global policy. In certain embodiments, for example, malware would have to independently compromise local policies on a first node and a second node of the plural nodes to alter authorized communications between the first node and the second node.

Certain embodiments may provide, for example, an application (for example a computer program product or a distributed computer program) and/or adaptation of one or more of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein and/or in one of the REFERENCE APPLICATIONS, or portions thereof, to improve (for example to secure) network communication around a distributed ledger and sub-components thereof.

A. In certain embodiments, for example, the network communication may comprise one or more network packets containing (a) one or more of the metadata, application process and data protocol metadata, identification codes, application identifiers, process identifiers, application process identifiers, user identifiers and/or codes, owner codes, user-application identifiers, process owner identifiers, application process identifiers, user-application process identifiers, data protocol identifiers and/or descriptors, payload data type descriptors and/or identifiers, payload data descriptors, file identification codes, policy identification codes, node identifiers and/or identification codes, device identifiers and/or codes, n-tuples and the like disclosed herein and/or in one of the REFERENCE APPLICATIONS; and (b) information. In certain embodiments, for example, the information may comprise part or all of a transaction (for example a confirmed transaction or an unconfirmed transaction), data to be inserted into a distributed ledger, a proposed block of transactions, gossip, a protocol message (for example a distributed ledger protocol message or a consensus protocol message), a result of a consensus vote, a rule (for example a consensus rule) a smart contract, instructions relative to a smart contract, mempool information (for example a mempool snapshot), a genesis block, ciphertext, a digital signature, a committed block, a distributed ledger, a hash value, a message from a wallet, a peer-to-peer message, a message for triggering a smart contract function, an update to a distributed ledger, a network security communication, a network security protocol message, a message generated by an implementation of a distributed ledger, a proof-of-work message, voting data, a read or write to a distributed ledger, a message in motion from outside a distributed ledger into the distributed ledger, an endorsed response (for example a digital signature) to a proposed transactions, block commitment information, a notification (for example a subscriber notification), a message from an ordering engine to a peer (for example a mining node), authentication information, authorization information, any of the foregoing information in encrypted or unencrypted form, communication pathway negotiation information, registration information, client data, private data, regulated data (for example HIPAA-regulated data), application programming interface information (for example the transaction, the data to be inserted into a distributed ledger, the proposed block of transactions, the gossip, the protocol messages, the results of consensus votes, the rules of a smart contract, the ciphertext, the digital signatures, the committed blocks, the distributed ledger, the hash values, the wallet messages, the peer-to-peer messages, the messages for triggering a smart contract function, the distributed ledger updates, the network security communications, the network security protocol messages, the messages generated by an implementation of a distributed ledger, the proof-of-work messages, the voting data, the reads or writes, the messages in motion from outside a distributed ledger into the distributed ledger, the endorsed responses, the block commitment information, the notifications, the messages from an ordering engine to a peer, the authentication information, the authorization information, the communication pathway negotiation information, the registration information, the client data, the private data, the regulated data, or application programming interface information disclosed in one or more of FIGS. 1-17), a copy of any of the foregoing, or two or more of the foregoing.

B. In certain embodiments, for example, the one or more network packets may comprise one or more of the metadata, application process and data protocol metadata, identification codes, application identifiers, process identifiers, application process identifiers, user identifiers and/or codes, owner codes, user-application identifiers, process owner identifiers, application process identifiers, user-application process identifiers, data protocol identifiers and/or descriptors, payload data type descriptors and/or identifiers, payload data descriptors, file identification codes, policy identification codes, node identifiers and/or identification codes, device identifiers and/or codes, n-tuples and the like disclosed herein and/or in one of the REFERENCE APPLICATIONS.

C. In certain embodiments, for example, at least a portion of the network packets (for example the information and/or the metadata) may be encrypted according to one of the cryptographic methods or in one or more of the REFERENCE APPLICATIONS.

D. In certain embodiments, for example, network security around a distributed ledger and/or sub-components thereof may be secured by network security software embodying one or more applications and/or adaptations of methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein and/or in one of the REFERENCE APPLICATIONS. In certain embodiments, for example, the network security software may be configured to perform any of the communication management operations disclosed herein and/or in one of the REFERENCE APPLICATIONS on network packets received from remote nodes on which the further network security software is performing further communication management operations any of the communication management operations disclosed herein and/or in one of the REFERENCE APPLICATIONS. In certain embodiments, for example, the network security software and the further network security software may perform at least a portion of the communication management operations necessary to establish, authorize, manage, and/or monitor any of the encrypted communication pathways and/or network tunnels disclosed herein and/or in one of the REFERENCE APPLICATIONS.

E. In certain embodiments, for example, a user node (for example a user node running a wallet app), a trader workstation, a subscriber node, a smart contract deployment server, a node holding a copy of a smart contract, an ordering engine, a mining node, a consensus node, a peer, a voting machine, a gateway node (for example a gateway node to a private blockchain), a mobile device, a server, a node within a private cloud, a node in a peer-to-peer network, a node holding a copy of a distributed ledger, a member of an overlay network (for example an I2P overlay network), a node in a fintech bank, a node in a distributed ledger ecosystem, or two or more of the foregoing (for example the user node, the trader workstation, the subscriber node, the smart contract deployment server, the node holding a copy of a smart contract, the ordering engine, the mining node, the consensus node, the peer, the voting machine, the gateway node, the mobile device, the server, the node within a private cloud, the node in a peer-to-peer network, the node holding a copy of a distributed ledger, the member of an overlay network, the node in a fintech bank, or the node in a distributed ledger ecosystem disclosed in one or more of FIGS. 1-17 may run network security software comprising one or more of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein or in one of the REFERENCE APPLICATIONS.

Certain embodiments may provide, for example, a product for securing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a first computing device to perform communication management operations, the communication management operations comprising: i) sending a nonpublic first identification code for the first computing device to a software port on a second computing device via a pre-established communication pathway; ii) receiving, in response to the sending the nonpublic first identification code, a nonpublic second identification code for the second computing device; iii) comparing the nonpublic second identification code with a pre-established value for the second computing device; iv) further sending a first application identifier for a first user-application to the second computing device via the pre-established communication pathway; v) further receiving, in response to the sending the first application identifier, a second application identifier for a second user-application; vi) comparing the second application identifier with a pre-established value for the second user-application; vii) confirming application data received from the second user-application conforms to a data model assigned to a predetermined port number, a data range assigned to the predetermined port number, and a command type assigned to the predetermined port number, the predetermined port number assigned to the first user-application and/or the second user-application; followed by viii) passing the confirmed application data to the first user-application.

A. In certain embodiments, for example, the nonpublic second identification code may be obtained from a network packet. In certain embodiments, for example, the nonpublic second identification code may be obtained from a portion of the network packet that is higher-than-OSI layer three and lower-than-OSI layer seven. In certain embodiments, for example, the comparing may be initiated in a kernel space of the first computing device.

B. In certain embodiments, for example, the pre-established value may be preprovisioned on nonvolatile storage media of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic second identification code with a single-use cryptographic key.

C. In certain embodiments, for example, the nonpublic first identification code and the nonpublic second identification code may be shared secrets between the first computing device and the second computing device.

D. In certain embodiments, for example, the communication management operations may further comprise translating, prior to the passing, the application data from a first pre-established format to a second pre-established format. In certain embodiments, for example, the communication management operations may further comprise: determining the first pre-established format and the second pre-established format from (a) a data model identification code assigned to the data model and/or (b) the predetermined port number.

E. In certain embodiments, for example, the communication management operations may further comprise: sending the first application identifier and a data model identifier assigned to the data model to the second computing device in a single network packet.

F. In certain embodiments, for example, the comparing the nonpublic second identification code and the comparing the second application identifier may be performed prior to any communication of application data between the first user-application and the second user-application.

G. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a data packet from a first port assigned to the first user-application, the first port hosted on the first computing device, the data packet comprising a payload and a second port number; and ii) assembling a packet segment for the received data packet, the packet segment comprising the payload, the first application identifier, and a data model identifier assigned to the data model. In certain embodiments, for example, the pre-established communication pathway may have a one-to-one correspondence to an n-tuple (as referred to herein, an n-tuple may be, for example, an at least a 2-tuple, an at least a 3-tuple, an at least a 5-tuple, an at least a 6-tuple, an at least an 8-tuple, an at least a 10-tuple, or an at least a 12-tuple) comprising the first application identifier, the second application identifier, the second port number, and the data model identifier. In certain embodiments, for example, each of a series of network packet communications of user-application data between the first port and the second port may comprise: transmission of a network packet to a third port, the third port assigned to network security software resident on the second computing device, the third port having a one-to-one correspondence with the second port number, the second port number assigned to the second port, the second port assigned to the second user-application, the network packet comprising the first application identifier and the data model identifier. In certain embodiments, for example, the first application identifier and the data model identifier in the each of the series of network packet communications may be encrypted by one of a series of single-use encryption keys. In certain embodiments, for example, all communications of user-application data between the first port and the second port may comprise the series of network packet communications.

H. In certain embodiments, for example, the communication management operations may further comprise: i) intercepting a network connection request from a first port assigned to the first user-application, the first port hosted by the first computing device, the request comprising a second port number; and ii) verifying that the first user-application is specifically authorized to communicate with a second port, the second port number assigned to the second port. In certain embodiments, for example, the verifying may be performed prior to forming the pre-established communication pathway.

I. In certain embodiments, for example, the communication management operations may further comprise: i) intercepting a network connection request from a second port, the second port hosted by the second computing device, the request comprising a first port number; and ii) verifying that a first port is specifically authorized to receive packet data from the second port, the first port number assigned to the first port. In certain embodiments, for example, the communication management operations may further comprise: confirming that the second computing device has consulted a pre-specified local policy to specifically authorize network packet communication between the first port and the second port. In certain embodiments, for example, the communication management operations may further comprise: receiving an encrypted identifier for the pre-specified local policy from the second computing device. In certain embodiments, for example, the pre-specified local policy may comprise a record, the record comprising the first application identifier, the second application identifier, the data model identifier, and the first port number. In certain embodiments, for example, the pre-specified local policy may further comprise a flag, the flag specifying whether the communication pathway is unidirectional or bidirectional. In certain embodiments, for example, the intercepting may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a network packet via the communication pathway, the network packet comprising the first port number, data from the second user-application, the second application identifier, and the data model identifier; and ii) comparing the second application identifier and the data model identifier with pre-established values, the pre-established values identified based on the first port number. In certain embodiments, for example, the second application identifier and the data model identifier may be located in higher-than-OSI layer three portions of the network packet. In certain embodiments, for example, the comparing may be initiated in a kernel of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: translating the data from the second user-application to a format expected by the first user-application.

J. In certain embodiments, for example, the communication management operations may further comprise: confirming that further application data received from the first user-application conforms to a further data model assigned to a further predetermined port number, a further data range assigned to the further predetermined port number, and a further command type assigned to the further predetermined port number, the further predetermined port number assigned to the first user-application and/or the second user-application; followed by passing the confirmed further application data to the second user-application.

K. In certain embodiments, for example, a portion of the communication management operations may be configured for execution in a kernel space of the first computing device, and a further portion of the communication management operations are configured for execution in an application space of the first computing device.

Certain embodiments may provide, for example, a product for securing communications of a plurality of networked computing devices (for example network packet-based communications among the network computing devices over a network), the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a first computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise sending a nonpublic first identification code (for example sending an encrypted nonpublic first identification code) for the first computing device (for example the nonpublic first identification code may be assigned to the first computing device) to a software port on a second computing device via a pre-established communication pathway. In certain embodiments, for example, the communication management operations may comprise receiving, in response to the sending (or in response to receipt of the nonpublic first identification code by the second computing device), a nonpublic second identification code for the second computing device (for example the nonpublic second identification code may be assigned to the second computing device). In certain embodiments, for example, the communication management operations may comprise comparing the nonpublic second identification code with a pre-established (or preconfigured, predefined, or preprovisioned) value for the second computing device (for example the pre-established value may be assigned to the second computing device).

A. In certain embodiments, for example, the nonpublic second identification code may be obtained from a network packet. In certain embodiments, for example, the nonpublic second identification code may be obtained from a higher-than-Open Systems Interconnection (OSI) layer three portion (for example one or more of an OSI layer four portion, an OSI layer five portion, an OSI layer six portion, an OSI layer seven portion, or a layer between one or more of an OSI layer three portion, an OSI layer four portion, an OSI layer five portion, an OSI layer six portion, or an OSI layer seven portion) of the network packet. In certain embodiments, for example, the comparing may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the comparing may be partially performed in an application space of the first computing device.

B. In certain embodiments, for example, the pre-established value may be preprovisioned on nonvolatile storage media of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic second identification code with a single-use cryptographic key. In certain embodiments, for example, the single-use cryptographic key may be rotated to obtain a further cryptographic key for use in further decrypting.

C. In certain embodiments, for example, the nonpublic first identification code and nonpublic second identification code may be shared secrets between the first computing device and the second computing device.

D. In certain embodiments, for example, the communication management operations may further comprise sending a first application identifier for a first user-application (for example the first application identifier may be assigned to the first user-application) to the second computing device via the pre-established communication pathway. In certain embodiments, for example, the communication management operations may further comprise receiving, in response to the sending, a second application identifier for a second user-application (for example the second application identifier may be assigned to the second user-application). In certain embodiments, for example, the communication management operations may further comprise comparing the second application identifier with a pre-established value for the second user-application. In certain embodiments, for example, the communication management operations may further comprise sending a data type identifier for the pre-established communication pathway via the pre-established communication pathway. In certain embodiments, for example, the communication management operations may further comprise receiving, in response to the sending, the data type identifier from the second computing device. In certain embodiments, for example, the communication management operations may further comprise comparing the received data type identifier with a pre-established value for the pre-established communication pathway. In certain embodiments, for example, the first application identifier and the data type identifier may be sent to the second computing device in a single network packet. In certain embodiments, for example, the comparing the nonpublic second identification code, the comparing the second application identifier, and the comparing the received data type identifier may be performed prior to any communication of application data between the first user-application and the second user-application. In certain embodiments, for example, the communication management operations may further comprise receiving a data packet from a first port assigned to the first user-application, the first port hosted on the first computing device, the data packet comprising a payload and a second port number. In certain embodiments, for example, the communication management operations may further comprise assembling a packet segment for the received data packet, the packet segment comprising the payload, the first application identifier, and the data type identifier. In certain embodiments, for example, the pre-established communication pathway may have a one-to-one correspondence to an n-tuple comprising the first application identifier, the second application identifier, the second port number, and the data type identifier. In certain embodiments, for example, each of a series of network packet communications of user-application data between the first port and the second port may comprise: transmission of a network packet to a third port, the third port assigned to network security software resident on the second computing device, the third port having a one-to-one correspondence with the second port number, the second port number assigned to the second port, the second port assigned to the second user-application, the network packet comprising the first application identifier and the data type identifier. In certain embodiments, for example, the first application identifier and the data type identifier in the each of the series of network packet communications may be encrypted by one of a series of single-use encryption keys. In certain embodiments, for example, all communications of user-application data between the first port and the second port may comprise the series of network packet communications. In certain embodiments, for example, the communication management operations may further comprise intercepting a network connection request from a first port assigned to the first user-application, the first port hosted by the first computing device, the request comprising a second port number. In certain embodiments, for example, the communication management operations may further comprise verifying that the first user-application is specifically authorized to communicate with a second port, the second port number assigned to the second port. In certain embodiments, for example, the verifying may be performed prior to forming the pre-established communication pathway. In certain embodiments, for example, the communication management operations may further comprise intercepting a network connection request from a second port, the second port hosted by the second computing device, the request comprising a first port number. In certain embodiments, for example, the communication management operations may further comprise verifying that a first port is specifically authorized to receive packet data from the second port, the first port number assigned to the first port. In certain embodiments, for example, the communication management operations may further comprise confirming that the second computing device has consulted a pre-specified local policy to specifically authorize network packet communication between the first port and the second port. In certain embodiments, for example, the communication management operations may further comprise: receiving an encrypted identifier for the pre-specified local policy from the second computing device. In certain embodiments, for example, the pre-specified local policy may comprise a record, the record comprising the first application identifier, the second application identifier, the data type identifier, and the first port number. In certain embodiments, for example, the pre-specified local policy may further comprise a flag, the flag specifying whether the communication pathway is unidirectional or bidirectional. In certain embodiments, for example, the intercepting may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the communication management operations may further comprise receiving a network packet via the communication pathway, the network packet comprising the first port number, data from the second user-application, the second application identifier, and the data type identifier. In certain embodiments, for example, the communication management operations may further comprise comparing the second application identifier and the data type identifier with pre-established values, the pre-established values identified based on the first port number. In certain embodiments, for example, the second application identifier and the data type identifier may be located in higher-than-OSI layer three portions (for example one or more of OSI layer four portions, OSI layer five portions, OSI layer six portions, OSI layer seven portions, or layers between one or more of the OSI layer three portions, OSI layer four portions, OSI layer five portions, OSI layer six portions, or OSI layer seven portions) of the network packet. In certain embodiments, for example, the comparing may be initiated in a kernel of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: translating the data from the second user-application to a format expected by the first user-application. In certain embodiments, for example, the data from the second user-application may be translated from a pre-established format, the pre-established format determined from the data type identifier.

E. In certain embodiments, for example, the communication management operations may comprise, prior to assembling the packet segment (and prior to one or more translation steps if the data undergoes translation), using the data type identifier to obtain a data definition for the payload or a portion of the payload, and evaluating the payload to determine whether the payload (or the portion of the payload) complies with the data definition. In certain embodiments, for example, the data definition may comprise a required protocol header (for example a header for an MQTT payload), a list (for example a list of one) of allowed data types (for example integer, text, or floating point data types), a required value pair (for example a field description and a value having a specified data type), and/or required control characters (for example one or more required ASCII code characters at predetermined positions in the payload). In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to transmit) the payload if the payload does not comply with the data definition. In certain embodiments, for example, the communication management operations may comprise, prior to assembling the packet segment, comparing the payload or portions of the payload based on the data type identifier against one or more pre-authorized ranges (for example minimum and/or maximum values and/or discrete allowed values for numerical data, or for example a range or allowed values for text data) and evaluating the payload to determine whether the payload (or the portion of the payload) falls within the one or more pre-authorized ranges. In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to transmit) the payload if the payload (or the portion of the payload) does not fall within the one or more pre-authorized ranges. In certain embodiments, for example, the communication management operations may comprise, prior to assembling the packet segment, using the data type identifier to obtain a list of pre-authorized commands and/or a list of prohibited commands (for example database instruction commands such as SQLread and SQLwrite), and evaluating the payload to determine whether the payload (or the portion of the payload) contains one of the pre-authorized commands and/or does not contain one of the prohibited commands. In certain further embodiments, for example, the list of pre-authorized commands may be exclusive. In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to transmit) the payload if the payload (or the portion of the payload) does not contain one of the pre-authorized commands and/or contains one of the prohibited commands.

F. In certain embodiments, for example, the communication management operations may comprise, after receiving the network packet via the communication pathway, using the data type identifier to obtain a data definition for the data from the second user-application or a portion thereof, and evaluating said data to determine whether the data (or the portion thereof) complies with the data definition. In certain embodiments, for example, the data definition may comprise a required protocol header (for example a header for an MQTT payload), a list (for example a list of one) of allowed data types (for example integer, text, or floating point data types), a required value pair (for example a field description and a value having a specified data type), and/or required control characters (for example one or more required ASCII code characters at predetermined positions in the payload). In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to transmit) the received network packet (including the data) if the data does not comply with the data definition. In certain embodiments, for example, the communication management operations may comprise, after receiving the network packet via the communication pathway, using the data type identifier to obtain one or more allowed ranges (for example minimum and/or maximum values and/or discrete allowed values for numerical data, or for example a range or allowed values for text data) for the data or a portion thereof, and evaluating the data to determine whether the data (or the portion thereof) falls within the one or more allowed ranges. In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to transmit) the data if the data (or the portion of the data) does not fall within the one or more allowed ranges. In certain embodiments, for example, the communication management operations may comprise, after receiving the network packet via the communication pathway, using the data type identifier to obtain a list of allowed commands and/or a list of prohibited commands (for example database instruction commands such as SQLread and SQLwrite), and evaluating the data to determine whether the data (or the portion of the data) contains one of the allowed commands and/or does not contain one of the prohibited commands. In certain further embodiments, for example, the list of allowed commands may be exclusive. In certain embodiments, for example, the communication management operations may comprise discarding (and taking no further steps to consume) the data if the data (or the portion of the data) does not contain one of the allowed commands and/or contains one of the prohibited commands.

G. In certain embodiments, for example, the nonpublic first identification code may be preprovisioned on the first computing device as a static value (for example in an encrypted configuration file) that is used each time the first computing device executes the communication management operations (and the nonpublic second identification code may be similarly preprovisioned on the second computing device) as described herein. In certain other embodiments, for example, the nonpublic first identification code (and/or nonpublic second identification code) may be obtained by requesting a security token (or token pair) for the first port (for example during establishment of the port in a listening mode, prior to sending a connection request, or during or after establishment of the pre-established communication pathway). In certain embodiments, for example, the request may specify identifiers (for example public identifiers) for the first computing device and the second computing device, and the token (or token pair) returned in response to the request may be a function of the first computing device and the second computing device. In certain embodiments, for example, the second computing device may also obtain a token (or token pair) complimentary to the token (or token pair) received by the first computing device. In certain embodiments, for example, a new token (or pair of tokens) is generated each time a connection between the first computing device and the second computing device is established. In certain embodiments, for example, all communications between the first computing device and the third computing device and all communications between the second computing device and the third computing device, are secured by one of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein.

H. In certain embodiments, for example, the application identifier for the first user-application may be preprovisioned on the first computing device as a static value (for example in an encrypted configuration file) that is used each time the first computing device executes the communication management operations (and the application identifier for the second user-application may be similarly preprovisioned on the second computing device) as described herein. In certain other embodiments, for example, the application identifier for the first user-application (and/or application identifier for the second user-application) may be obtained by requesting a security token (or token pair) for the first port (for example during establishment of the port in a listening mode, prior to sending a connection request, or during or after establishment of the pre-established communication pathway). In certain embodiments, for example, the request may specify identifiers for the first user-application and the second user-application (and optionally the data type), and the token (or token pair) returned in response to the request may be a function of the identifiers for the first user-application and the second user-application (and optionally the data type). In certain embodiments, for example, the second computing device may also obtain a token (or token pair) complimentary to the token (or token pair) received by the first computing device. In certain embodiments, for example, a new token (or pair of tokens) is generated each time a connection between the first computing device and the second computing device is established. In certain embodiments, for example, all communications between the first computing device and the third computing device and all communications between the second computing device and the third computing device, are secured by one of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein.

I. In certain embodiments, for example, all authentication and authorization parameters required to perform the communication management operations may be obtained from a local encrypted configuration file installed on a first node (for example the first computing device). In certain embodiments, for example, the local encrypted configuration file may include only those authentication and authorization parameters required by the first node to conduct pre-authorized communications. In certain other embodiments, for example, at least a portion (for example all) authentication and authorization parameters required to perform the communication management operations (whether static parameters or dynamically generated tokens or token pairs) may be obtained from a third node (for example a credentialing server). In certain embodiments, for example, the communication management operations may comprise obtaining the nonpublic first identification code, the pre-established value for the second computing device, the first application identifier, the pre-established value for the second user-application, the data type identifier, the pre-established value for the received data type identifier, the first port number, the second port number, the third port number, the data definition, the protocol header, the list of allowed data types, the required value pair, the required control characters, the one or more allowed ranges, the list of allowed commands, and/or the list of prohibited commands from at least a third node (for example a credentialing server). In certain embodiments, for example, one or more (for example all) of the nonpublic first identification code, the pre-established value for the second computing device, the first application identifier, the pre-established value for the second user-application, the data type identifier, the pre-established value for the received data type identifier, the first port number, the second port number, the third port number, the data definition, the protocol header, the list of allowed data types, the required value pair, the required control characters, the one or more allowed ranges, the list of allowed commands, and the list of prohibited commands may be obtained upon request, periodically, on boot-up of the first node or the third node, or upon establishment of a communication pathway between the first node and the third node. In certain embodiments, for example, two or more (for example all) of the nonpublic first identification code, the pre-established value for the second computing device, the first application identifier, the pre-established value for the second user-application, the data type identifier, the pre-established value for the received data type identifier, the first port number, the second port number, the third port number, the data definition, the protocol header, the list of allowed data types, the required value pair, the required control characters, the one or more allowed ranges, the list of allowed commands, and the list of prohibited commands may be obtained simultaneously, essentially simultaneously, or sequentially. In certain embodiments, for example, a portion or all the obtaining may be performed during boot up of the first computing device (including for example, obtaining all necessary parameters for communicating with remote computing devices at boot up of the first computing devices). In certain embodiments, for example, a portion or all of the obtaining may be performed dynamically (for example in response to a confirmation that a communication pathway has been established (for example upon establishment of the pre-established communication pathway). In certain embodiments, for example, the third node may maintain a master configuration file of a portion or all necessary authentication and authorization parameters for port-to-port communications between a plurality of networked computing devices.

J. In certain embodiments, for example, a portion of the communication management operations may be configured for execution in a kernel space of the first computing device, and a further portion of the communication management operations may be configured for execution in an application space of the first computing device.

Certain embodiments may provide, for example, a product for securing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a first computing device to perform communication management operations, the communication management operations comprising: i) sending a nonpublic first identification code for the first computing device to a software port on a second computing device via a pre-established communication pathway; ii) receiving, in response to the sending, a nonpublic second identification code for the second computing device; and iii) comparing the nonpublic second identification code with a pre-established value for the second computing device.

A. In certain embodiments, for example, the nonpublic second identification code may be obtained from a network packet. In certain embodiments, for example, the nonpublic second identification code may be obtained from a higher-than-OSI layer three portion (for example one or more of an OSI layer four portion, an OSI layer five portion, an OSI layer six portion, an OSI layer seven portion, or a layer between one or more of an OSI layer three portion, an OSI layer four portion, an OSI layer five portion, an OSI layer six portion, or an OSI layer seven portion) of the network packet. In certain embodiments, for example, the comparing may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the comparing may be partially performed in an application space of the first computing device.

B. In certain embodiments, for example, the pre-established value may be preprovisioned on nonvolatile storage media of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: decrypting the nonpublic second identification code with a single-use cryptographic key. In certain embodiments, for example, the single-use cryptographic key may be rotated to obtain a further cryptographic key for use in further decrypting.

C. In certain embodiments, for example, the nonpublic first identification code and nonpublic second identification code may be shared secrets between the first computing device and the second computing device.

D. In certain embodiments, for example, the communication management operations may further comprise: i) sending a first application identifier for a first user-application to the second computing device via the pre-established communication pathway; ii) receiving, in response to the sending, a second application identifier for a second user-application; and iii) comparing the second application identifier with a pre-established value for the second user-application. In certain embodiments, for example, the communication management operations may further comprise: i) sending a data type identifier for the pre-established communication pathway via the pre-established communication pathway; ii) receiving, in response to the sending, the data type identifier from the second computing device; and iii) comparing the received data type identifier with a pre-established value for the pre-established communication pathway. In certain embodiments, for example, the first application identifier and the data type identifier may be sent to the second computing device in a single network packet. In certain embodiments, for example, the comparing the nonpublic second identification code, the comparing the second application identifier, and the comparing the received data type identifier may be performed prior to any communication of application data between the first user-application and the second user-application. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a data packet from a first port assigned to the first user-application, the first port hosted on the first computing device, the data packet comprising a payload and a second port number; and ii) assembling a packet segment for the received data packet, the packet segment comprising the payload, the first application identifier, and the data type identifier. In certain embodiments, for example, the pre-established communication pathway may have a one-to-one correspondence to an n-tuple comprising the first application identifier, the second application identifier, the second port number, and the data type identifier. In certain embodiments, for example, each of a series of network packet communications of user-application data between the first port and a second port may comprise: the first application identifier and the data type identifier, the second port assigned to the second user-application, the second port number assigned to the second port. In certain embodiments, for example, the first application identifier and the data type identifier in the each of the series of network packet communications may be encrypted by one of a series of single-use encryption keys. In certain embodiments, for example, the series of network packet communications may comprise all network packet communications of user-application data between the first port and the second port. In certain embodiments, for example, the communication management operations may further comprise: i) intercepting a network connection request from a first port assigned to the first user-application, the first port hosted by the first computing device, the request comprising a second port number; and ii) verifying that the first user-application is specifically authorized to communicate with a second port, the second port number assigned to the second port. In certain embodiments, for example, the verifying may be performed prior to forming the pre-established communication pathway. In certain embodiments, for example, the communication management operations may further comprise: i) intercepting a network connection request from a second port, the second port hosted by the second computing device, the request comprising a first port number; and ii) verifying that a first port is specifically authorized to receive packet data from the second port, the first port number assigned to the first port. In certain embodiments, for example, the communication management operations may further comprise confirming that the second computing device has consulted a pre-specified local policy to specifically authorize network packet communication between the first port and the second port. In certain embodiments, for example, the communication management operations may further comprise: receiving an encrypted identifier for the pre-specified local policy from the second computing device. In certain embodiments, for example, the pre-specified local policy may comprise a record, the record comprising the first application identifier, the second application identifier, the data type identifier, and the first port number. In certain embodiments, for example, the pre-specified local policy may further comprise a flag, the flag specifying whether the communication pathway is unidirectional or bidirectional. In certain embodiments, for example, the intercepting may be initiated in a kernel space of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: i) receiving a network packet via the communication pathway, the network packet comprising the first port number, data from the second user-application, the second application identifier, and the data type identifier; and ii) comparing the second application identifier and the data type identifier with pre-established values, the pre-established values identified based on the first port number. In certain embodiments, for example, the second application identifier and the data type identifier may be located in higher-than-OSI layer three portions (for example one or more of OSI layer four portions, OSI layer five portions, OSI layer six portions, OSI layer seven portions, or layers between one or more of the OSI layer three portions, OSI layer four portions, OSI layer five portions, OSI layer six portions, or OSI layer seven portions) of the network packet. In certain embodiments, for example, the comparing may be initiated in a kernel of the first computing device. In certain embodiments, for example, the communication management operations may further comprise: translating the data from the second user-application to a format expected by the first user-application. In certain embodiments, for example, the data from the second user-application may be translated from a pre-established format, the pre-established format determined from the data type identifier.

E. In certain embodiments, for example, a portion of the communication management operations may be configured for execution in a kernel space of the first computing device, and a further portion of the communication management operations may be configured for execution in an application space of the first computing device.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels (for example network tunnels based on protocol which involve encrypting a network packet and inserting the encrypted network packet inside a packet for transport (such as IPsec protocol), or network tunnels based on Socket Secured Layer protocol, or network tunnels which require encryption of part of all of a packet payload but do not involve additional headers (for example do not involve packaging an IP packet inside another IP packet) for network communication on all port-to-port network communications (for example unencrypted or encrypted payload communications) among the plurality of networked computing devices (inclusive, for example, of port-to-port communications according to User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) between end-user application processes over a network)). In certain embodiments, for example, the port-to-port communications may be between user-application processes (inclusive of application processes having a process owner (or user)). In certain embodiments, for example, one or more of the user-application processes may reside in kernel and/or application space. In certain embodiments, for example, the establishing may comprise intercepting network connection requests (for example by network application programming interfaces) having associated destination port numbers. In certain embodiments, for example, the establishing may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers (for example predefined tunnel port numbers associated with servers), comprising identifying at least one (for example, one) preconfigured, predefined, pre-established and/or preprovisioned tunnel port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers (and also, for example, cipher suite parameters), each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers. In certain embodiments, for example, the establishing may comprise authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers (for example user-application identifiers derived from application process identifiers and/or application process owners, together or in parts), and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the computing device identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

A. In certain embodiments, for example, the intercepting, identifying, requesting, and authorizing may be transparent to all user-application processes (for example all processes (except optionally for processes executing portions of the program code) executing in (non-kernel) application space and having process owners) on the plurality of networked computing devices. In certain embodiments, for example, the intercepting may be performed by a network application programming interface having standard syntax (for example using modified network application programming interface functions that retain standard syntax, for example: bind( ) connect( ) listen( ) UDP sendto( ), UDP bindto( ), and close( ) functions).

B. In certain embodiments, for example, the intercepting, identifying, requesting, and authorizing may be self-executing. In certain further embodiments, for example, the intercepting, identifying, requesting, and authorizing may be automatic. In certain further embodiments, for example, the identifying, requesting, and authorizing may be automatically invoked following the intercepting. In certain embodiments, for example, the intercepting, identifying, and authorizing may occur in the kernel spaces of the plurality of networked computing devices. In certain embodiments, for example, one or more of the intercepting, identifying, and authorizing may occur in application spaces of the plurality of networked computing devices. In certain further embodiments, for example, at least a portion (for example all) of the non-transitory computer-readable storage medium may be resident on a deployment server.

C. In certain further embodiments, for example, at least a portion (for example, all) of the non-transitory computer-readable storage medium may be resident on flash drive. In certain embodiments, for example, the communication management operations may further comprise: preventing all user-application process ports from binding to a portion or all physical interfaces of the plurality of networked computing devices.

D. In certain embodiments, for example, user-application process ports may transmit packets to network security software process ports by loopback interfaces. In certain embodiments, for example, user-application process ports may transmit packets to network security software process ports by TUN/TAP interfaces.

E. In certain embodiments, for example, the network tunnels may be encrypted. In certain embodiments, for example, the network tunnels may be interposed between network security processes (for example middleware) running on separate computing devices. In certain embodiments, for example, the network security processes may manage a segment of the data pathway that is interposed between user-application processes on separate computing devices of the plurality of networked computing devices. In certain embodiments, for example, the network security processes may be conducted on the plural computing devices with user-application processes, wherein the user-application processes may engage in port-to-port communications. In certain embodiments, for example, the network security processes may be resident on different computing devices from the user-application processes. In certain embodiments, for example, the product may be used to configure a software-defined perimeter.

F. In certain embodiments, for example, the tunnel port numbers, computing device identifiers, user-application identifiers, and/or payload data-type identifiers may be obtained from a plurality of configuration files. In certain embodiments, for example, the configuration files may contain private keys for negotiating encryption keys for the network tunnels. In certain embodiments, for example, the configuration files may be binary files. In certain embodiments, for example, the configuration files may be encrypted files. In certain embodiments, for example, the configuration files may be variable length files. In certain embodiments, for example, the configuration files may be read-only files.

G. In certain embodiments, for example, the communication management operations may further comprise: executing operating system commands to identify user-application processes making the connection requests, and verifying that the identified user-application processes are authorized to transmit data to the associated destination port numbers. In certain embodiments, for example, the communication management operations may further comprise thwarting attempts by malware to form network connections, the thwarting comprising: rejecting network connection requests in which identified user-application processes are not authorized to transmit data, for example by reference to a configuration file of authorized port-to-port connections. In certain embodiments, for example, the product may further comprise a configuration file, the configuration file comprising at least two of the following: tunnel port numbers, computing device identifiers, user-application identifiers, and payload data-type identifiers. In certain embodiments, for example, the communication management operations may comprise updating a connection state indicator based on the comparing computing device identifiers, the comparing user-application process identifiers, and/or the comparing payload data-type identifiers. In certain embodiments, for example, the updated connection state indicator may be a field in a list of port-to-port connections. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that no connection has been established to a value indicating that an open connection state exists for a particular port-to-port connection. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that no connection has been established to a value indicating that a connection is in the process of being formed and that one or more of the computing device identifiers, the user-application process identifiers, and/or the payload data-type identifiers has been successfully exchanged, authenticated and/or authorized. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that an open connection exists, that no connection exists, or that a connection is in the process of being formed to a value indicating that the connection is being declined due to failure to successfully exchange, authenticate and/or authorize one or more of the computing device identifiers, the user-application process identifiers, and/or the payload data-type identifiers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all (or substantially all, or most or greater than 80% or greater than 90% of the connected or operational physical ports across all the devices within the software defined network) port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, comprising identifying at least one tunnel port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers; and iv) authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels for all port-to-port network communications among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting a network connection request having an associated destination port number. In certain embodiments, for example, the establishing may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number. In certain embodiments, for example, the establishing may comprise requesting the forming of a network tunnel, the forming comprising sending a connection request packet comprising the tunnel port number. In certain embodiments, for example, the establishing may comprise authorizing the network tunnel, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) requesting the forming of a network tunnel, the forming comprising sending a connection request packet comprising the tunnel port number; and iv) authorizing the network tunnel, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels for at least one port-to-port network communication (including, for example, all port-to-port network communications (for example unencrypted or encrypted payload communications) among the plurality of networked computing devices (inclusive, for example, of port-to-port communications according to User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) between end-user application processes over a network)). In certain embodiments, for example, the port-to-port communications may be between user-application processes (inclusive of application processes having a process owner (or user)). In certain embodiments, for example, one or more of the user-application processes may reside in kernel and/or application space. In certain embodiments, for example, the establishing may comprise intercepting network connection requests from source ports (for example the source ports may comprise ports associated with user-application processes), the requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the computing device identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers; and iv) authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for at least one port-to-port network communication (for example all port-to-port communications) among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting network connection requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for at least one port-to-port network communication (including, for example, all port-to-port network communications) among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting network connection requests from source ports (for example source ports that have been opened by and have a predetermined relationship with authorized applications), the requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels for all port-to-port network communications among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting a network connection request from a source port, the request having an associated destination port number. In certain embodiments, for example, the establishing may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the establishing may comprise requesting the negotiation of a network tunnel, comprising sending a connection request packet comprising the associated destination port number. In certain embodiments, for example, the establishing may comprise authorizing the network tunnel, comprising comparing a computing device identifiers, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of a network tunnel, comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the network tunnel, comprising comparing a computing device identifiers, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting a network connection request having an associated destination port number. In certain embodiments, for example, the establishing may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number associated with the destination port number. In certain embodiments, for example, the establishing may comprise requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the encrypted communication port number. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number associated with the destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the encrypted communication port number; and iv) authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting a network connection request from a source port, the request having an associated destination port number. In certain embodiments, for example, the establishing may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the establishing may comprise requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked computing devices, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise: receiving data packets (for example from a user-application process via a loopback interface) having payloads and associated destination port numbers (the associated destination port numbers may include, for example, a destination port number associated with a destination port of a network security process). In certain embodiments, for example, the performing communication processing functions may comprise: identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise: assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor. In certain embodiments, for example, the associated user-application process identifier may comprise a process identifier and/or a process owner. In certain embodiments, for example, the associated user-application process identifier, and a payload data type descriptor may be combined (or concatenated) in a metadata portion of the packet segment. In certain embodiments, for example, the metadata may be encrypted, for example by a single-use cryptographic key. In certain embodiments, for example, the performing communication processing functions may comprise: requesting transmission of network packets through network tunnels (for example at least a different network tunnel for each application-to-application communication of a specified data protocol type), each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

A. In certain embodiments, for example, the receiving, identifying, assembling, and requesting may be transparent to all user-application processes on the plurality of networked computing devices. In certain embodiments, for example, the data packets may be received by loopback interfaces. In certain embodiments, for example, the data packets may be received by kernel read and/or write calls. In certain embodiments, for example, the data packets may be received by TAP/TUN interfaces. In certain embodiments, for example, the receiving may occur in kernel spaces of the plural computing devices. In certain embodiments, for example, the receiving may occur in application spaces of the plural computing devices. In certain embodiments, for example, the received data packet may be received from user-application processes executing in application spaces of the plural computing devices. In certain embodiments, for example, the user-application process identifiers may comprise process commands and process owners (for example process commands and process owners comparable to the output of operating system commands). In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if more than a fixed number (for example a fixed number such as 10 or 20) of requests to transmit network packets are rejected. In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if the difference between rejected and successful requests to transmit network packets exceeds a fixed number (for example a fixed number such as 10 or 20).

B. In certain embodiments, for example, the communication processing functions may further comprise: checking a connection status of the network tunnels (for example by checking lists maintained in kernel memory of the plural networked computing devices). In certain embodiments, for example, the communication processing functions may further comprise dropping network packets that are received via one or more network tunnels whose connection status indicators are set to a non-operative state.

C. In certain embodiments, for example, the payloads may be translated into a common format prior to the assembling.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving a data packet having a payload and an associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number. In certain embodiments, for example, the performing communication processing functions may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of a network packet through a network tunnel, the network packet comprising the tunnel port number and the assembled packet segment, the network tunnel having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the tunnel port number and the assembled packet segment, the network tunnel having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

A. In certain embodiments, for example, the transmitted network packets may be exclusive of the destination port numbers associated with the received data packets. In certain embodiments, for example, the payloads in the transmitted network packets may be re-associated with the destination port numbers only after the transmitted network packets are received at one or more second computing devices of the plurality of networked computing devices, the second computing device different from the computing device. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device to one or more second computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted across a network coupled to one or more computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device via the network tunnels.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets, the data packets comprising messages and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

A. In certain embodiments, for example, one or more of the messages may have a size exceeding a maximum transfer unit.

B. In certain embodiments, for example, one of the packet segments may comprise a portion of one of the messages, the one of the messages having a size exceeding a maximum transfer unit and the one of the packet segments having a total payload, the total payload having a size not exceeding the maximum transfer unit or another maximum transfer unit.

Certain embodiments may provide, for example product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets, the data packets comprising messages and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets, the data packets comprising messages and associated destination port numbers, the messages comprising user-application identifiers and payload data type descriptors. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, the at least a portion of one of the messages comprising one of the user-application identifiers and one of the payload data type descriptors. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

A. In certain embodiments, for example, the user-application identifiers may be spaced apart from one another and the payload data type descriptors are spaced apart from one another.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets, the data packets comprising messages and associated destination port numbers, the messages comprising user-application identifiers and payload data type descriptors; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, the at least a portion of one of the messages comprising one of the user-application identifiers and one of the payload data type descriptors; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

A. In certain embodiments, for example, any given message to be sent across a network may have a size exceeding a maximum transfer unit (for example a maximum transfer unit of 1500 bytes), requiring the message to be split into plural payloads for transport across the network, each of the plural payloads having a size of no greater than the maximum transfer unit, for insertion into plural network packets. In certain further embodiments, for example, the computing processing functions may comprise inserting plural metadata into the message, whereby each one of the plural payloads contains one of the plural metadata. In certain embodiments, for example, the plural metadata may be positioned at predetermined locations in the plural payloads. In certain embodiments, for example, two or more of the plural metadata may be spaced a pre-determined distance in the any given message. In certain embodiments, for example, each one of the plural meta data may comprise one of the user-application identifiers and one of the payload data type descriptors.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

A. In certain embodiments, for example, the transmitted network packets may be exclusive of the destination port numbers associated with the received data packets. In certain embodiments, for example, the payloads in the transmitted network packets may be re-associated with the destination port numbers only after the transmitted network packets are received at one or more second computing devices of the plurality of networked computing devices, the second computing device different from the computing device. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device to one or more second computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted across a network coupled to one or more computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device via the encrypted communication pathways.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising. In certain embodiments, for example, the communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the communication processing functions may comprise requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

A. In certain embodiments, for example, the transmitted network packets may be exclusive of the destination port numbers associated with the received data packets. In certain embodiments, for example, the payloads in the transmitted network packets may be re-associated with the destination port numbers only after the transmitted network packets are received at one or more second computing devices of the plurality of networked computing devices, the second computing device different from the computing device. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device to one or more second computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted across a network coupled to one or more computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port numbers may not be transmitted from the computing device via the network tunnels.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving a data packet from a source port, the data packet having a payload and an associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of a network packet through a network tunnel, the network packet comprising the associated destination port numbers and the assembled packet segment, the network tunnels having a one-to-one correspondence with the associated destination port number.

A. In certain embodiments, for example, the transmitted network packet may be exclusive of the destination port number associated with the received data packet. In certain embodiments, for example, the payload in the transmitted network packet may be re-associated with the destination port number only after the transmitted network packet is received at a second computing devices of the plurality of networked computing devices, the second computing device different from the computing device. In certain embodiments, for example, the associated destination port number may not be transmitted from the computing device to the second computing device of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port number may not be transmitted across a network coupled to one or more computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port number may not be transmitted from the computing device via the network tunnel.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor, and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the associated destination port numbers and the assembled packet segment, the network tunnels having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving a data packet having a payload and an associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned port number, the port number having a one-to-one correspondence with the associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting encrypted communication over an encrypted communication pathway of a network packet, the network packets comprising the port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned port number, the port number having a one-to-one correspondence with the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting encrypted communication over an encrypted communication pathway of a network packet, the network packets comprising the port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise receiving a data packet from a source port, the data packet having a payload and an associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the performing communication processing functions may comprise assembling a packet segment, the packet segments comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of a network packet through an encrypted communication pathway, the network packets comprising the associated destination port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the associated destination port number.

A. In certain embodiments, for example, the transmitted network packet may be exclusive of the destination port number associated with the received data packet. In certain embodiments, for example, the payload in the transmitted network packet may be re-associated with the destination port number only after the transmitted network packet is received at a second computing devices of the plurality of networked computing devices, the second computing device different from the computing device. In certain embodiments, for example, the associated destination port number may not be transmitted from the computing device to the second computing device of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port number may not be transmitted across a network coupled to one or more computing devices of the plurality of networked computing devices. In certain embodiments, for example, the associated destination port number may not be transmitted from the computing device via the network tunnel.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of computing devices, the performing communication processing functions comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segments comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through an encrypted communication pathway, the network packets comprising the associated destination port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: performing communication processing functions on at least a portion of network-to-port communications (including, for example, on all network-to-port communications) received by the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise obtaining tunnel port numbers, metadata (for example metadata encrypted using a single-use cryptographic key), and payloads associated with network packets. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the tunnel port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application process identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained tunnel port numbers. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packets, comprising: comparing (for example comparing in application spaces or kernel spaces of the plurality of computing devices) metadata with the authorization codes. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission (for example across loopback interfaces, by TUN/TAP interfaces, or by kernel read and/or write calls) of payloads from the authorized network packets to destinations referenced by the destination port numbers. In certain embodiments, for example, the payloads may be passed to the destination port numbers by one or more loopback interfaces.

A. In certain embodiments, for example, the obtaining, identifying, authorizing, and requesting may be transparent to all user-application processes on the plurality of networked computing devices (for example by employing modified network application programming interface functions (for example in a modified operating system) while maintaining standard syntax). In certain embodiments, for example, the obtaining, identifying, authorizing, and requesting may be self-executing and/or automatic (for example requiring no human intervention, no interruption in computer execution other than ordinary, temporary process scheduling).

B. In certain embodiments, for example, the communication processing functions may be performed at 95% of wire speed or greater and less than 10% of the processor load may be committed to network communications. In certain embodiments, for example, the destinations may comprise user-application processes. In certain embodiments, for example, the program code may be middleware positioned between the network and the destinations referenced by the destination port number. In certain embodiments, for example, the communication processing functions may further comprise: dropping network packets if they are not authorized following the comparing (for example dropping network packets for which the metadata does not match expected values based on the authorization codes).

C. In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if more than a fixed number of network packets are not authorized following the comparing. In certain embodiments, for example, the communication processing functions may further comprise: checking, the checking at least partially performed in kernels of the plural networked computing devices, a connection status of the network. In certain embodiments, for example, the communication processing functions may further comprise: dropping network packets that are received via one or more network tunnels whose connection status indicators are set to a non-operative state.

Certain embodiments may comprise, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of computing devices, the performing communication processing functions comprising: i) obtaining tunnel port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the tunnel port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained tunnel port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all network-to-port communications received by the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device. In certain embodiments, for example, the performing communication processing functions may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packet, comprising: comparing the metadata with the authorization code. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of the payload to a destination referenced by the destination port number.

Certain embodiments may comprise, for example, a computer program product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of computing devices, the performing communication processing functions comprising: i) obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: performing communication processing functions on at least a portion of network-to-port communications (including, for example, on all network-to-port communications) received by the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise obtaining destination port numbers, metadata, and payloads associated with network packets. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of computing devices, the performing communication processing functions comprising: i) obtaining destination port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all network-to-port communications received by the plurality of computing devices. In certain embodiments, for example, the performing communication processing functions may comprise obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device. In certain embodiments, for example, the performing communication processing functions may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packet, comprising: comparing the metadata with the authorization code. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of the payload to a destination referenced by the preconfigured, predefined, pre-established and/or preprovisioned destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of computing devices, the performing communication processing functions comprising: i) obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the preconfigured, predefined, pre-established and/or preprovisioned destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having a plurality of computer-readable program code embodied therein, the plurality of computer-readable program code for distributed execution across the plurality of networked computing devices to cooperatively enable and/or cause the plurality of networked computing devices to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program code of the plurality of computer-readable program code. In certain embodiments, for example, the communication management operations may comprise negotiating, on a second computing device, a second data pathway between a second network security program of the plurality of computer-readable program code and a second user-application. In certain embodiments, for example, the communication management operations may comprise negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted network tunnel, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having a plurality of computer-readable program code embodied therein, the plurality of computer-readable program code for distributed execution across the plurality of networked computing devices to cooperatively enable and/or cause the plurality of networked computing devices to perform communication management operations, the communication management operations comprising: i) negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program code of the plurality of computer-readable program code; ii) negotiating, on a second computing device, a second data pathway between a second network security program of the plurality of computer-readable program code and a second user-application; and iii) negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted network tunnel, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having a plurality of computer-readable program code embodied therein, the plurality of computer-readable program code for distributed execution across the plurality of networked computing devices to cooperatively enable and/or cause the plurality of networked computing devices to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program of the plural security programs. In certain embodiments, for example, the communication management operations may comprise negotiating, on a second computing device, a second data pathway between a second network security program of the plural security programs and a second user-application. In certain embodiments, for example, the communication management operations may comprise negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted communication pathway, each of the first data pathway, second data pathway, and third data pathway exclusive to a dedicated data pathway for communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having a plurality of computer-readable program code embodied therein, the plurality of computer-readable program code for distributed execution across the plurality of networked computing devices to cooperatively enable and/or cause the plurality of networked computing devices to perform communication management operations, the communication management operations comprising: i) negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program of the plural security programs; ii) negotiating, on a second computing device, a second data pathway between a second network security program of the plural security programs and a second user-application; iii) negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted communication pathway, each of the first data pathway, second data pathway, and third data pathway exclusive to a dedicated data pathway for communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a secured system, comprising: i) a first node networked with a second node, the first node hosting a first application program, the second node hosting a second application program; and ii) plural network security programs cooperatively configured according to plural configuration files to negotiate one or plural dedicated data pathways for all communications between the first application program and the second application program, each of the one or plural data pathways comprising: an encrypted network tunnel extending from a first network security program of the plural network security programs to a second network security program of the plural network security programs, the first network security program and the second network security program interposed between the first application program and the second application program; each of the plural configuration files comprising: a) one or plural destination port numbers associated with the second application program; b) one or plural destination port numbers associated with the second network security program, comprising at least one port number for each one of the one or plural destination port numbers associated with the second application program; c) one or plural first user-application identifiers associated with the first application program; d) one or plural second user-application identifiers associated with the second application program; e) one or plural data type identifiers; and f) node identification codes for the first node and the second node, processor, or computing device.

Certain embodiments may provide, for example, a secured system, comprising: i) a first node networked with a second node, the first node hosting a first application program, the second node hosting a second application program; and ii) plural network security programs cooperatively configured according to plural configuration files to negotiate one or plural dedicated data pathways for all communications between the first application program and the second application program, each of the one or plural data pathways comprising: an encrypted communication pathway extending from a first network security program of the plural network security programs to a second network security program of the plural network security programs, the first network security program and the second network security program interposed between the first application program and the second application program; each of the plural configuration files comprising: a) one or plural destination port numbers associated with the second application program; b) one or plural first user-application identifiers associated with the first application program; c) one or plural second user-application identifiers associated with the second application program; d) one or plural data type identifiers; and e) node identification codes for the first node and the second node, processor, or computing device.

Certain embodiments may provide, for example, a secured system, comprising: i) a first node networked with a second node, a) the first node hosting a first application program, a first configuration file and a first network security program associated with the first configuration file; and b) the second node hosting a second application program, a second configuration file, and a second network security program associated with the second configuration file; and ii) the first and second network security programs cooperatively configured to negotiate one or plural dedicated data pathways for all communications between the first application program and the second application program, a) each of the one or plural data pathways comprising the first network security program and the second network security program interposed between the first application program and the second application program; and b) each of the one or plural data pathways comprising: an encrypted network tunnel between the first network security program and the second network security program, each of the plural configuration files comprising at least one of the following: a) one or plural destination port numbers associated with the second application program; b) one or plural destination port numbers associated with the second network security program, comprising at least one port number for each one of the one or plural destination port numbers associated with the second application program; c) one or plural first user-application identifiers associated with the first application program; d) one or plural second user-application identifiers associated with the second application program; e) one or plural data type identifiers; and f) node identification codes for the first node and the second node, processor, or computing device.

Certain embodiments may provide, for example, a secured system, comprising: i) a first node networked with a second node, a) the first node hosting a first application program, a first configuration file and a first network security program associated with the first configuration file; and b) the second node hosting a second application program, a second configuration file, and a second network security program associated with the second configuration file; and ii) the first and second network security programs cooperatively configured to negotiate one or plural dedicated data pathways for all communications between the first application program and the second application program, a) each of the one or plural data pathways comprising the first network security program and the second network security program interposed between the first application program and the second application program; and b) each of the one or plural data pathways comprising: an encrypted data pathway between the first network security program and the second network security program, each of the plural configuration files comprising at least one of the following: a) one or plural destination port numbers associated with the second application program; b) one or plural first user-application identifiers associated with the first application program; c) one or plural second user-application identifiers associated with the second application program; d) one or plural data type identifiers; and e) node identification codes for the first node and the second node, processor, or computing device.

Certain embodiments may provide, for example, a product for managing communications in a cloud, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all network-to-port communications received by a virtual machine. In certain embodiments, for example, the performing communication processing functions may comprise obtaining port numbers, metadata, and payloads associated with network packets. In certain embodiments, for example, the performing communication processing functions may comprise identifying predefined destination port numbers and predefined authorization codes associated with the obtained port numbers, each one of the predefined authorization codes comprising a predefined user-application identifier and a predefined payload data-type identifier associated with one of the obtained port numbers. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packets, comprising: comparing at least a portion of the metadata with the predefined authorization codes. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of payloads from the authorized network packets to cloud resources referenced by the predefined destination port numbers.

Certain embodiments may provide, for example, a product for managing communications in a cloud, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by a virtual machine, the performing communication processing functions comprising: i) obtaining port numbers, metadata, and payloads associated with network packets; ii) identifying predefined destination port numbers and predefined authorization codes associated with the obtained port numbers, each one of the predefined authorization codes comprising a predefined user-application identifier and a predefined payload data-type identifier associated with one of the obtained port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the predefined authorization codes; and iv) requesting transmission of payloads from the authorized network packets to cloud resources referenced by the predefined destination port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting network connection requests (for example by network application programming interfaces) having associated destination port numbers. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers (for example predefined tunnel port numbers associated with servers), comprising identifying at least one (for example, one) preconfigured, predefined, pre-established and/or preprovisioned tunnel port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the method may comprise requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers (and also, for example, cipher suite parameters), each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers. In certain embodiments, for example, the method may comprise authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers (for example user-application identifiers derived from application process identifiers and/or application process owners, together or in parts), and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the computing device identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, comprising identifying at least one tunnel port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers; and iv) authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting a network connection request having an associated destination port number. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number. In certain embodiments, for example, the method may comprise requesting the forming of a network tunnel, the forming comprising sending a connection request packet comprising the tunnel port number. In certain embodiments, for example, the method may comprise authorizing the network tunnel, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) requesting the forming of a network tunnel, the forming comprising sending a connection request packet comprising the tunnel port number; and iv) authorizing the network tunnel, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting network connection requests from source ports (for example the source ports may comprise ports associated with user-application processes), the requests having associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the computing device identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers; and iv) authorizing the network tunnels, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting network connection requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for at least one port-to-port network communication (including, for example, all port-to-port network communications) among the plurality of networked computing devices. In certain embodiments, for example, the establishing may comprise intercepting network connection requests from source ports (for example source ports that have been opened by and have a predetermined relationship with authorized applications), the requests having associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers. In certain embodiments, for example, the method may comprise authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting a network connection request from a source port, the request having an associated destination port number. In certain embodiments, for example, the method may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the method may comprise may comprise requesting the negotiation of a network tunnel, comprising sending a connection request packet comprising the associated destination port number. In certain embodiments, for example, the method may comprise authorizing the network tunnel, comprising comparing a computing device identifiers, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of a network tunnel, comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the network tunnel, comprising comparing a computing device identifiers, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting a network connection request having an associated destination port number. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number associated with the destination port number. In certain embodiments, for example, the method may comprise requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the encrypted communication port number. In certain embodiments, for example, the method may comprise authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number associated with the destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the encrypted communication port number; and iv) authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise intercepting a network connection request from a source port, the request having an associated destination port number. In certain embodiments, for example, the method may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the method may comprise requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number. In certain embodiments, for example, the method may comprise authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the encrypted communication pathway, comprising comparing a computing device identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise receiving data packets (for example from a user-application process via a loopback interface) having payloads and associated destination port numbers (the associated destination port numbers may include, for example, a destination port number associated with a destination port of a network security process). In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor. In certain embodiments, for example, the associated user-application process identifier may comprise a process identifier and/or a process owner. In certain embodiments, for example, the associated user-application process identifier, and a payload data type descriptor may be combined (or concatenated) in a metadata portion of the packet segment. In certain embodiments, for example, the metadata may be encrypted, for example by a single-use cryptographic key. In certain embodiments, for example, the method may comprise requesting transmission of network packets through network tunnels (for example at least a different network tunnel for each application-to-application communication of a specified data protocol type), each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise receiving a data packet having a payload and an associated destination port number. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number. In certain embodiments, for example, the method may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of a network packet through a network tunnel, the network packet comprising the tunnel port number and the assembled packet segment, the network tunnel having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the tunnel port number and the assembled packet segment, the network tunnel having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets, the data packets comprising messages and associated destination port numbers. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise may comprise assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets, the data packets comprising messages and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets, the data packets comprising messages and associated destination port numbers, the messages comprising user-application identifiers and payload data type descriptors. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, the at least a portion of one of the messages comprising one of the user-application identifiers and one of the payload data type descriptors. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets, the data packets comprising messages and associated destination port numbers, the messages comprising user-application identifiers and payload data type descriptors; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising at least a portion of one of the messages, the at least a portion of one of the messages comprising one of the user-application identifiers and one of the payload data type descriptors; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving a data packet from a source port, the data packet having a payload and an associated destination port number. In certain embodiments, for example, the method may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the method may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of a network packet through a network tunnel, the network packet comprising the associated destination port numbers and the assembled packet segment, the network tunnels having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor, and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the associated destination port numbers and the assembled packet segment, the network tunnels having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise receiving data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned port numbers, each one of the port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the port numbers.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise receiving a data packet having a payload and an associated destination port number. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned port number, the port number having a one-to-one correspondence with the associated destination port number. In certain embodiments, for example, the method may comprise assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting encrypted communication over an encrypted communication pathway of a network packet, the network packets comprising the port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned port number, the port number having a one-to-one correspondence with the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting encrypted communication over an encrypted communication pathway of a network packet, the network packets comprising the port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the port number.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the method may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the method may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise receiving a data packet from a source port, the data packet having a payload and an associated destination port number. In certain embodiments, for example, the method may comprise verifying that the source port is authorized to communicate with a port having the associated destination port number. In certain embodiments, for example, the method may comprise assembling a packet segment, the packet segments comprising the payload, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the method may comprise requesting transmission of a network packet through an encrypted communication pathway, the network packets comprising the associated destination port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segments comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through an encrypted communication pathway, the network packets comprising the associated destination port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise obtaining port numbers, metadata (for example metadata encrypted using a single-use cryptographic key), and payloads associated with network packets. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the obtained port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application process identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained port numbers. In certain embodiments, for example, the method may comprise authorizing the network packets, comprising: comparing (for example comparing in application spaces or kernel spaces of the plurality of computing devices) metadata with the authorization codes. In certain embodiments, for example, the method may comprise requesting transmission (for example across loopback interfaces, by TUN/TAP interfaces, or by kernel read and/or write calls) of payloads from the authorized network packets to destinations referenced by the destination port numbers. In certain embodiments, for example, the payloads may be passed to the destination port numbers by one or more loopback interfaces.

Certain embodiments may provide, for example, a method for managing communications, comprising: performing communication processing functions on all network-to-port communications received by the plurality of computing devices, the performing communication processing functions comprising: i) obtaining port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the obtained port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number. In certain embodiments, for example, the method may comprise authorizing the network packet, comprising: comparing the metadata with the authorization code. In certain embodiments, for example, the method may comprise requesting transmission of the payload to a destination referenced by the destination port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the destination port number.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise obtaining destination port numbers, metadata, and payloads associated with network packets. In certain embodiments, for example, the method may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers. In certain embodiments, for example, the method may comprise authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes. In certain embodiments, for example, the method may comprise requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) obtaining destination port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a method for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the method may comprise obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device. In certain embodiments, for example, the method may comprise identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number. In certain embodiments, for example, the method may comprise authorizing the network packet, comprising: comparing the metadata with the authorization code. In certain embodiments, for example, the method may comprise requesting transmission of the payload to a destination referenced by the preconfigured, predefined, pre-established and/or preprovisioned destination port number.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) obtaining a port number, metadata, and a payload associated with a network packet received by the networked computing device; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the obtained port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the preconfigured, predefined, pre-established and/or preprovisioned destination port number.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program code of a plurality of computer-readable program code. In certain embodiments, for example, the method may comprise negotiating, on a second computing device, a second data pathway between a second network security program of the plurality of computer-readable program code and a second user-application. In certain embodiments, for example, the method may comprise negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted network tunnel, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program code of a plurality of computer-readable program code; ii) negotiating, on a second computing device, a second data pathway between a second network security program of the plurality of computer-readable program code and a second user-application; and iii) negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted network tunnel, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a method for managing communications. In certain embodiments, for example, the method may comprise negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program of plural security programs. In certain embodiments, for example, the method may comprise negotiating, on a second computing device, a second data pathway between a second network security program of the plural security programs and a second user-application. In certain embodiments, for example, the method may comprise negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted communication pathway, each of the first data pathway, second data pathway, and third data pathway exclusive to a dedicated data pathway for communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) negotiating, on a first computing device, a first data pathway between a first user-application and a first network security program of plural security programs; ii) negotiating, on a second computing device, a second data pathway between a second network security program of the plural security programs and a second user-application; iii) negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising an encrypted communication pathway, each of the first data pathway, second data pathway, and third data pathway exclusive to a dedicated data pathway for communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a method for managing communications in a cloud. In certain embodiments, for example, the method may comprise obtaining port numbers, metadata, and payloads associated with network packets. In certain embodiments, for example, the method may comprise identifying predefined destination port numbers and predefined authorization codes associated with the obtained port numbers, each one of the predefined authorization codes comprising a predefined user-application identifier and a predefined payload data-type identifier associated with one of the obtained port numbers. In certain embodiments, for example, the method may comprise authorizing the network packets, comprising: comparing at least a portion of the metadata with the predefined authorization codes. In certain embodiments, for example, the method may comprise requesting transmission of payloads from the authorized network packets to cloud resources referenced by the predefined destination port numbers.

Certain embodiments may provide, for example, a method for managing communications, comprising: i) obtaining port numbers, metadata, and payloads associated with network packets; ii) identifying predefined destination port numbers and predefined authorization codes associated with the obtained port numbers, each one of the predefined authorization codes comprising a predefined user-application identifier and a predefined payload data-type identifier associated with one of the obtained port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the predefined authorization codes; and iv) requesting transmission of payloads from the authorized network packets to cloud resources referenced by the predefined destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes. In certain embodiments, for example, the product may comprise a computer-readable storage medium (for example a non-transitory computer-readable storage medium) having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels (for example network tunnels based on protocol which involve encrypting a network packet and inserting the encrypted network packet inside a packet for transport (such as IPsec protocol), or network tunnels based on Socket Secured Layer protocol, or network tunnels which require encryption of part of all of a packet payload but do not involve additional headers (for example do not involve packaging an IP packet inside another IP packet) for network communication) on all port-to-port network communications (for example unencrypted or encrypted payload communications) among the plurality of networked processor nodes (inclusive, for example, of port-to-port communications according to User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) between end-user application processes over a network)). In certain embodiments, for example, the port-to-port communications may be between user-application processes (inclusive of application processes having a process owner (or user)). In certain embodiments, for example, one or more of the user-application processes may reside in kernel and/or application space. In certain embodiments, for example, the establishing may comprise intercepting network connection requests (for example by network application programming interfaces) having associated destination port numbers. In certain embodiments, for example, the establishing may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers (for example predefined tunnel port numbers associated with servers), comprising identifying at least one (for example, one) preconfigured, predefined, pre-established and/or preprovisioned tunnel port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers (and also, for example, cipher suite parameters), each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers. In certain embodiments, for example, the establishing may comprise authorizing the network tunnels, comprising comparing node identifiers, user-application identifiers (for example user-application identifiers derived from application process identifiers and/or application process owners, together or in parts), and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the node identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

A. In certain embodiments, for example, the intercepting, identifying, requesting, and authorizing may be transparent to all user-application processes (for example all processes (except optionally for processes executing portions of the program code) executing in (non-kernel) application space and having process owners) on the plurality of networked nodes. In certain embodiments, for example, the intercepting may be performed by a network application programming interface having standard syntax (for example using modified network application programming interface functions that retain standard syntax, for example: bind( ) connect( ) listen( ) UDP sendto( ), UDP bindto( ), and close( ) functions).

B. In certain embodiments, for example, the intercepting, identifying, requesting, and authorizing may be self-executing. In certain further embodiments, for example, the intercepting, identifying, requesting, and authorizing may be automatic. In certain further embodiments, for example, the identifying, requesting, and authorizing may be automatically invoked following the intercepting. In certain embodiments, for example, the intercepting, identifying, and authorizing may occur in the kernel spaces of the plurality of networked nodes. In certain embodiments, for example, one or more of the intercepting, identifying, and authorizing occur in application spaces of the plurality of networked nodes. In certain further embodiments, for example, at least a portion (for example all) of the non-transitory computer-readable storage medium may be resident on a deployment server.

C. In certain further embodiments, for example, at least a portion (for example all) of the non-transitory computer-readable storage medium may be resident on flash drive. In certain embodiments, for example, the communication management operations may further comprise: preventing all user-application process ports from binding to a portion or all physical interfaces of the plurality of networked nodes.

D. In certain embodiments, for example, user-application process ports may transmit packets to network security software process ports by loopback interfaces. In certain embodiments, for example, user-application process ports may transmit packets to network security software process ports by TUN/TAP interfaces.

E. In certain embodiments, for example, the network tunnels may be encrypted. In certain embodiments, for example, the network tunnels may be interposed between network security processes (for example middleware) running on separate nodes. In certain embodiments, for example, the network security processes may manage a segment of the data pathway that is interposed between user-application processes on separate nodes of the plurality of networked processor nodes. In certain embodiments, for example, the network security processes may be conducted on the plural nodes with user-application processes, wherein the user-application processes may engage in port-to-port communications. In certain embodiments, for example, the network security processes may be resident on different nodes from the user-application processes. In certain embodiments, for example, the product may be used to configure a software-defined perimeter.

F. In certain embodiments, for example, the tunnel port numbers, node identifiers, user-application identifiers, and/or payload data-type identifiers may be obtained from a plurality of configuration files. In certain embodiments, for example, the configuration files may contain private keys for negotiating encryption keys for the network tunnels. In certain embodiments, for example, the configuration files may be binary files. In certain embodiments, for example, the configuration files may be encrypted files. In certain embodiments, for example, the configuration files may be variable length files. In certain embodiments, for example, the configuration files may be read-only files.

G. In certain embodiments, for example, the communication management operations may further comprise: executing operating system commands to identify user-application processes making the connection requests, and verifying that the identified user-application processes are authorized to transmit data to the associated destination port numbers. In certain embodiments, for example, the communication management operations may further comprise thwarting attempts by malware to form network connections, the thwarting comprising: rejecting network connection requests in which identified user-application processes are not authorized to transmit data, for example by reference to a configuration file of authorized port-to-port connections. In certain embodiments, for example, the product may further comprise a configuration file, the configuration file comprising at least two of the following: tunnel port numbers, node identifiers, user-application identifiers, and payload data-type identifiers. In certain embodiments, for example, the communication management operations may comprise updating a connection state indicator based on the comparing node identifiers, the comparing user-application process identifiers, and/or the comparing payload data-type identifiers. In certain embodiments, for example, the updated connection state indicator may be a field in a list of port-to-port connections. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that no connection has been established to a value indicating that an open connection state exists for a particular port-to-port connection. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that no connection has been established to a value indicating that a connection is in the process of being formed and that one or more of the node identifiers, the user-application process identifiers, and/or the payload data-type identifiers has been successfully exchanged, authenticated and/or authorized. In certain embodiments, for example, the connection state indicator may be changed from a value indicating that an open connection exists, that no connection exists, or that a connection is in the process of being formed to a value indicating that the connection is being declined due to failure to successfully exchange, authenticate and/or authorize one or more of the node identifiers, the user-application process identifiers, and/or the payload data-type identifiers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for at least one port-to-port network communication (inclusive, for example, of all port-to-port network communications) among the plurality of networked processor nodes, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, comprising identifying at least one tunnel port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of network tunnels, the requesting comprising sending connection request packets comprising the tunnel port numbers, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers; and iv) authorizing the network tunnels, comprising comparing node identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a computer program product for managing communications of a networked node comprising a processor, the computer program product comprising a computer-readable storage medium (for example a non-transitory computer-readable storage medium) having computer-readable program code embodied therein, the computer-readable program code executable by the processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications for the networked node, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) requesting the forming of a network tunnel, the forming comprising sending a connection request packet comprising the tunnel port number; and iv) authorizing the network tunnel, comprising comparing a node identifier, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes. In certain embodiments, for example, the product may comprise a computer-readable storage medium (for example a non-transitory computer-readable storage medium) having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized network tunnels for at least one port-to-port network communication (including, for example, all port-to-port network communications (for example unencrypted or encrypted payload communications) among the plurality of networked processor nodes (inclusive, for example, of port-to-port communications according to User Datagram Protocol (UDP) or Transmission Control Protocol (TCP) between end-user application processes over a network)). In certain embodiments, for example, the port-to-port communications may be between user-application processes (inclusive of application processes having a process owner (or user)). In certain embodiments, for example, one or more of the user-application processes may reside in kernel and/or application space. In certain embodiments, for example, the establishing may comprise intercepting network connection requests from source ports (for example the source ports may comprise ports associated with user-application processes), the requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise authorizing the network tunnels, comprising comparing node identifiers, user-application identifiers, and/or payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes. In certain further embodiments, for example, the node identifiers, user-application identifiers, and/or payload data-type identifiers may be encrypted and require decryption before the comparing.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of network tunnels, comprising sending connection request packets comprising the associated destination port numbers, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers; and iv) authorizing the network tunnels, comprising comparing node identifiers, user-application identifiers, and payload data-type identifiers received from the network tunnels with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for at least one port-to-port network communication (for example all port-to-port communications) among the plurality of networked processor nodes. In certain embodiments, for example, the establishing may comprise intercepting network connection requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathways, comprising comparing node identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port numbers, comprising identifying at least one preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number for each associated destination port number of the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the encrypted communication port numbers, each one of the encrypted communication pathways having a one-to-one correspondence with one of the encrypted communication port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing node identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise establishing authorized encrypted communication pathways for at least one port-to-port network communication (including, for example, all port-to-port network communications) among the plurality of networked processor nodes. In certain embodiments, for example, the establishing may comprise intercepting network connection requests from source ports (for example source ports that have been opened by and have a predetermined relationship with authorized applications), the requests having associated destination port numbers. In certain embodiments, for example, the establishing may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the establishing may comprise requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers. In certain embodiments, for example, the establishing may comprise authorizing the encrypted communication pathways, comprising comparing node identifiers, user-application identifiers, and/or payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) requesting the negotiation of encrypted communication pathways, the requesting comprising sending connection request packets comprising the associated destination port numbers; and iv) authorizing the encrypted communication pathways, comprising comparing node identifiers, user-application identifiers, and payload data-type identifiers received from the encrypted communication pathways with preconfigured, predefined, pre-established and/or preprovisioned authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of a network tunnel, comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the network tunnel, comprising comparing a node identifiers, a user-application identifier, and a payload data-type identifier received from the network tunnel with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting a network connection request having an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned encrypted communication port number associated with the destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the encrypted communication port number; and iv) authorizing the encrypted communication pathway, comprising comparing a node identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: establishing authorized network tunnels for all port-to-port network communications among the plurality of networked processor nodes, comprising: i) intercepting a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) requesting the negotiation of an encrypted communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number; and iv) authorizing the encrypted communication pathway, comprising comparing a node identifier, a user-application identifier, and a payload data-type identifier received from the encrypted communication pathway with a preconfigured, predefined, pre-established and/or preprovisioned authorization code.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise: receiving data packets (for example from a user-application process via a loopback interface) having payloads and associated destination port numbers (the associated destination port numbers may include, for example, a destination port number associated with a destination port of a network security process). In certain embodiments, for example, the performing communication processing functions may comprise: identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise: assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor. In certain embodiments, for example, the associated user-application process identifier may comprise a process identifier and/or a process owner. In certain embodiments, for example, the associated user-application process identifier, and a payload data type descriptor may be combined (or concatenated) in a metadata portion of the packet segment. In certain embodiments, for example, the metadata may be encrypted, for example by a single-use cryptographic key. In certain embodiments, for example, the performing communication processing functions may comprise: requesting transmission of network packets through network tunnels (for example at least a different network tunnel for each application-to-application communication of a specified data protocol type), each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

A. In certain embodiments, for example, the receiving, identifying, assembling, and requesting may be transparent to all user-application processes on the plurality of networked nodes. In certain embodiments, for example, the data packets may be received by loopback interfaces. In certain embodiments, for example, the data packets may be received by kernel read and/or write calls. In certain embodiments, for example, the data packets may be received by TAP/TUN interfaces. In certain embodiments, for example, the receiving may occur in kernel spaces of the plural nodes. In certain embodiments, for example, the receiving may occur in application spaces of the plural nodes. In certain embodiments, for example, the received data packet may be received from user-application processes executing in application spaces of the plural nodes. In certain embodiments, for example, the user-application process identifiers may comprise process commands and process owners (for example process commands and process owners comparable to the output of operating system commands). In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if more than a fixed number (for example a fixed number such as 10 or 20) of requests to transmit network packets are rejected. In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if the difference between rejected and successful requests to transmit network packets exceeds a fixed number (for example a fixed number such as 10 or 20).

B. In certain embodiments, for example, the communication processing functions may further comprise: checking a connection status of the network tunnels (for example by checking lists maintained in kernel memory of the plural networked nodes). In certain embodiments, for example, the communication processing functions may further comprise dropping network packets that are received via one or more network tunnels whose connection status indicators are set to a non-operative state.

C. In certain embodiments, for example, the payloads may be translated into a common format prior to the assembling.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application process identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a computer program product for managing communications of a networked node comprising a processor, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by the processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the networked node, the performing communication processing functions comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number associated with the destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the tunnel port number and the assembled packet segment, the network tunnel having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of port-to-network communications (including, for example, on all port-to-network communications) of the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise receiving data packets from source ports, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through network tunnels, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the network tunnels having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor, and iv) requesting transmission of a network packet through a network tunnel, the network packet comprising the associated destination port numbers and the assembled packet segment, the network tunnels having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned tunnel port numbers, each one of the tunnel port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a tunnel port number of one of the tunnel port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the tunnel port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving a data packet having a payload and an associated destination port number; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned tunnel port number, the tunnel port number having a one-to-one correspondence with the associated destination port number; iii) assembling a packet segment, the packet segment comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting encrypted communication over an encrypted communication pathway of a network packet, the network packets comprising the tunnel port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the tunnel port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving data packets from source ports, the data packets having payloads and associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of network packets through encrypted communication pathways, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments, each one of the encrypted communication pathways having a one-to-one correspondence with one of the associated destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving a data packet from a source port, the data packet having a payload and an associated destination port number; ii) verifying that the source port is authorized to communicate with a port having the associated destination port number; iii) assembling a packet segment, the packet segments comprising the payload, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of a network packet through an encrypted communication pathway, the network packets comprising the associated destination port number and the assembled packet segment, the encrypted communication pathway having a one-to-one correspondence with the associated destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a computer-readable storage medium (for example a non-transitory computer-readable storage medium) having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of network-to-port communications (including, for example, on all network-to-port communications) received by the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise obtaining tunnel port numbers, metadata (for example metadata encrypted using a single-use cryptographic key), and payloads associated with network packets. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the tunnel port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application process identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained tunnel port numbers. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packets, comprising: comparing (for example comparing in application spaces or kernel spaces of the plurality of nodes) metadata with the authorization codes. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission (for example across loopback interfaces, by TUN/TAP interfaces, or by kernel read and/or write calls) of payloads from the authorized network packets to destinations referenced by the destination port numbers. In certain embodiments, for example, the payloads may be passed to the destination port numbers by one or more loopback interfaces.

A. In certain embodiments, for example, the obtaining, identifying, authorizing, and requesting may be transparent to all user-application processes on the plurality of networked nodes (for example by employing modified network application programming interface functions (for example in a modified operating system) while maintaining standard syntax). In certain embodiments, for example, the obtaining, identifying, authorizing, and requesting may be self-executing and/or automatic (for example requiring no human intervention, no interruption in computer execution other than ordinary, temporary process scheduling).

B. In certain embodiments, for example, the communication processing functions may be performed at 95% of wire speed or greater and less than 10% of the processor load may be committed to network communications. In certain embodiments, for example, the destinations may comprise user-application processes. In certain embodiments, for example, the program code may be middleware positioned between the network and the destinations referenced by the destination port number. In certain embodiments, for example, the communication processing functions may further comprise: dropping network packets if they are not authorized following the comparing (for example dropping network packets for which the metadata does not match expected values based on the authorization codes).

C. In certain embodiments, for example, the communication processing functions may further comprise: setting connection status indicators to a non-operative state if more than a fixed number of network packets are not authorized following the comparing. In certain embodiments, for example, the communication processing functions may further comprise: checking, the checking at least partially performed in kernels of the plural networked nodes, a connection status of the network. In certain embodiments, for example, the communication processing functions may further comprise: dropping network packets that are received via one or more network tunnels whose connection status indicators are set to a non-operative state.

Certain embodiments may comprise, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of network-to-port communications (including, for example, on all network-to-port communications) received by the plurality of processor nodes, the performing communication processing functions comprising: i) obtaining tunnel port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned destination port numbers and preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the tunnel port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the obtained tunnel port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may comprise, for example, a computer program product for managing communications of a networked nodes comprising a processor, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by the processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the networked node, the performing communication processing functions comprising: i) obtaining a tunnel port number, metadata, and a payload associated with a network packet received by the networked node; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the tunnel port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained tunnel port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the destination port number.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a computer-readable storage medium (for example a non-transitory computer-readable storage medium) having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on at least a portion of network-to-port communications (including, for example, on all network-to-port communications) received by the plurality of processor nodes. In certain embodiments, for example, the performing communication processing functions may comprise obtaining destination port numbers, metadata, and payloads associated with network packets. In certain embodiments, for example, the performing communication processing functions may comprise identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers. In certain embodiments, for example, the performing communication processing functions may comprise authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes. In certain embodiments, for example, the performing communication processing functions may comprise requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of processor nodes, the performing communication processing functions comprising: i) obtaining destination port numbers, metadata, and payloads associated with network packets; ii) identifying preconfigured, predefined, pre-established and/or preprovisioned authorization codes associated with the destination port numbers, each one of the authorization codes comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with one of the destination port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked processor nodes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable by a processor to perform communication management operations, the communication management operations comprising: performing communication processing functions on all network-to-port communications received by the plurality of processor nodes, the performing communication processing functions comprising: i) obtaining a tunnel port number, metadata, and a payload associated with a network packet received by the networked node; ii) identifying a preconfigured, predefined, pre-established and/or preprovisioned destination port number and a preconfigured, predefined, pre-established and/or preprovisioned authorization code associated with the tunnel port number, the authorization code comprising a preconfigured, predefined, pre-established and/or preprovisioned user-application identifier and a preconfigured, predefined, pre-established and/or preprovisioned payload data-type identifier associated with the obtained tunnel port number; iii) authorizing the network packet, comprising: comparing the metadata with the authorization code; and iv) requesting transmission of the payload to a destination referenced by the preconfigured, predefined, pre-established and/or preprovisioned destination port number.

Certain embodiments may provide, for example, a method for authorized network communication, comprising: detecting a request by a first application present on a first node to transmit data to a destination port associated with a second application present on a second node, validating the authority of the first application to transmit the data to the destination port at least by checking a preconfigured list present on the first node, passing the data from the first application to a first middleware on the first node, and mutual authorization and authentication of the first node and the second node, the first application and the second application, and a data protocol of the data. In certain further embodiments, for example, the method may further comprise transmitting a network packet containing the data through a network tunnel (for example a network tunnel configured according to User Datagram Protocol (UDP), a “mid-weight” UDP comprising UDP plus additional connection acknowledgments devised to increase reliability of a UDP connection, or Transmission Control Protocol (TCP)), the network tunnel extending from the first middleware to a second middleware present on the second node, the network tunnel initialized based on the detected request, the initialization based at least on the mutual authentication and authorization.

A. In certain embodiments, for example, the first node may be a first computing device. In certain embodiments, for example, the first node may comprise a first processor, a first kernel, a first network stack, a first loopback interface, a first network application programming interface of the first network stack, and a first non-transitory computer-readable storage medium. In certain embodiments, for example, the second node may comprise a second processor, a second kernel, a second network stack, and a second non-transitory computer-readable storage medium. In certain embodiments, for example, the detecting may be performed by a first execution thread being executed by the first processor, and at least a portion of the validating may be performed by a second execution thread being executed by the first processor. In certain embodiments, for example, the detecting and the validating may be performed by a first execution thread being executed by the first processor, and at least a portion of the mutual authorization and authentication may be performed by a second execution thread being executed by the first processor. In certain embodiments, for example, the validating may be performed by the first middleware. In certain embodiments, for example, execution of the first middleware may be distributed at least between a first execution thread and a second execution thread being executed by the first processor. In certain embodiments, for example, the request from the first application may be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the request from the first application may not be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the request from the first application may be passed through a shim in the first network stack to the first middleware. In certain embodiments, for example, the request from the first application may be passed from the first network application programming interface directly to the first middleware. In certain embodiments, for example, the data may be passed through the loopback interface to the first middleware. In certain embodiments, for example, the data may not be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the data may be passed through a shim in the first network stack to the first middleware. In certain embodiments, for example, the data may be passed from the first network application programming interface directly to the first middleware. In certain embodiments, for example, the detecting may comprise receiving (or intercepting), by the first middleware, the request. In certain embodiments, for example, the detecting may occur in the first network stack. In certain embodiments, for example, the detecting may occur in the first network application programming interface.

B. In certain embodiments, for example, at least a portion of the first middleware may comprise a kernel driver. In certain embodiments, for example, at least a portion of the first middleware may comprise a kernel module process.

C. In certain embodiments, for example, the method may further comprise: preventing the first application and the second application from associating with any socket comprising a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the first application from binding with a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the second application from binding with a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the first application from binding with a physical interface, preventing any port associated with the second application from binding with a physical interface.

D. In certain embodiments, for example, the network tunnel may be encrypted. In certain further embodiments, for example, at least a portion of the network packet (for example the payload, a portion of the payload, or a metadata portion of the payload) may be encrypted using a symmetric key algorithm (for example a symmetric key algorithm such as an Advanced Encryption Standard (AES) algorithm (for example 256-bit AES). In certain further embodiments, for example, the symmetric key may be obtained by executing a key exchange algorithm (for example Elliptic-Curve Diffie-Hellman (ECDH) key exchange). In certain further embodiments, for example, the symmetric key may be a single-use key. In certain further embodiments, for example, the symmetric key may be obtained by rotating a key derived from ECDH key exchange.

E. In certain embodiments, for example, the data protocol may be obtained from metadata present in the network packet. In certain further embodiments, for example, the metadata may be encrypted.

F. In certain embodiments, for example, the metadata may comprise a connection state indicator for the network tunnel. In certain embodiments, for example, a connection state indicator for the network tunnel may be inserted into the metadata by the first middleware. In certain embodiments, for example, a second middleware present on the second node may determine a connection state of the network tunnel by inspecting the metadata (for example by decrypting encrypted metadata followed by parsing the metadata).

G. In certain embodiments, for example, at least a portion of the validating (for example all of the validating) may be performed by the first middleware. In certain further embodiments, for example, validating may comprise the first middleware inspecting a connection state of the network tunnel (for example checking a port state of an endpoint of the network tunnel such as a network tunnel endpoint present on the first node). In certain embodiments, for example, validating may comprise matching a 2-tuple comprising a destination port number of the destination port and a unique first application identifier of the first application with record present in the preconfigured list.

H. In certain embodiments, for example, the network tunnel may be encrypted based on executing an encryption algorithm (for example encrypted based on executing a key exchange algorithm) and the mutual authentication and authorization of the first node and the second node may be performed separately from the executing the encryption algorithm (for example may be performed after the executing the encryption algorithm). In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may comprise encrypting a first node identification code using a cryptographic key derived from the executing the key exchange algorithm. In certain further embodiments, for example, the cryptographic key may be nonpublic (for example the cryptographic key may be a shared secret between the first middleware and a second middleware executing on the second node). In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may comprise: (a) encrypting a first node identification code using a first cryptographic key derived from the executing the key exchange algorithm, and (b) encrypting a second node identification code using a second cryptographic key (for example a second cryptographic key that is different from the first cryptographic key) derived from the executing the key exchange algorithm. In certain further embodiments, for example, the cryptographic key may be nonpublic (for example the first cryptographic key and the second cryptographic key may each be a shared secret between the first middleware and a second middleware executing on the second node).

I. In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may be independent of mutual authentication and authorization of the first application and the second application and/or mutual authentication and authorization of the data protocol. In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may be independent of initializing the network tunnel. In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may occur after the network tunnel is initialized. In certain embodiments, for example, the exchange of the data protocol identifier between the first node and the second node may occur during initialization of the network tunnel to at least partially authorize the network tunnel.

J. In certain embodiments, for example, mutual authorization and authentication of the first application and the second application may comprise key exchange (for example by execution of a key exchange algorithm such as ECDH) during initialization of the network tunnel. In certain embodiments, for example, a first private key associated with the first application and a second private key associated with the second application may be used during the key exchange. In certain embodiments, for example, the first private key may be uniquely associated with the first application and the second private key may be uniquely associated with the second application. In certain embodiments, for example, the first private key may be uniquely associated with the first application and a user (for example a single-user) of the first application and the second private key may be uniquely associated with the second application and a user (for example a single-user) of the second application.

K. In certain embodiments, for example, mutual authorization and authentication of the first application and the second application may comprise encrypting a unique first application identifier and sending the encrypted unique first application identifier from the first node to the second node, followed by decrypting the unique first application identifier and comparing the unique first application identifier to a predetermined first identifier value that is specific to the network tunnel. In certain further embodiments, for example, mutual authorization and authentication of the first application and the second application may comprise encrypting a unique second application identifier and sending the encrypted unique second application identifier from the second node to the first node, followed by decrypting the unique second application identifier and comparing the unique second application identifier to a predetermined second identifier value that is specific to the network tunnel. In certain embodiments, for example, the unique first application identifier may comprise a first application identifier and an associated first user identifier. In certain embodiments, for example, the unique second application identifier may comprise a second application identifier and an associated second user identifier. In certain embodiments, for example, the unique first application identifier and the unique second application identifier may be exchanged during initialization of the network tunnel to at least partially authorize the network tunnel. In certain embodiments, for example, the network packet may contain the unique first application identifier. In certain embodiments, for example, mutual authentication and authorization of the data protocol may further comprise encrypting a data protocol identifier and sending the encrypted data protocol identifier from the first node to the second node, followed by decrypting the data protocol identifier and comparing the data protocol identifier to a predetermined data protocol identifier value that is specific to the network tunnel. In certain further embodiments, for example, mutual authorization and authentication of data protocol may comprise encrypting a data protocol identifier and sending the encrypted data protocol identifier from the second node to the first node, followed by decrypting the data protocol identifier and comparing the data protocol identifier to a predetermined data protocol identifier value that is specific to the network tunnel. In certain embodiments, for example, the above-described exchange of the data protocol identifier between the first node and the second may be performed during initialization of the network tunnel to at least partially authorize the network tunnel. In certain embodiments, for example, the network packet may contain the unique first application identifier. In certain embodiments, for example, mutual authentication and authorization of the first application and second application and mutual authentication and authorization of the data protocol may be combined. In certain further embodiments, for example, a first combined identifier comprising the unique first application identifier and the data protocol identifier may be encrypted and sent from the from the first node to the second node, followed by decrypting the first combined identifier and comparing the first combined identifier to a predetermined first combined identifier value that is specific to the network tunnel. In certain further embodiments, for example, a second combined identifier comprising the unique second application identifier and the data protocol identifier may be encrypted and sent from the from the second node to the first node, followed by decrypting the second combined identifier and comparing the second combined identifier to a predetermined second combined identifier value that is specific to the network tunnel. In certain embodiments, for example, the first combined identifier and the second combined identifier may be exchanged during initialization of the network tunnel to at least partially authorize the network tunnel. In certain embodiments, for example, the network packet may contain the unique first application identifier. In certain embodiments, for example, the first application identifier and the first user identifier may be obtained from a process status request (for example a “ps” command in Linux).

L. In certain embodiments, for example, the method may comprise detecting a request by the second application to open a port. In certain embodiments, for example, the method may comprise validating the authority of the second application to open the port at least by checking a further preconfigured list present on the second node, processor, or computing device. In certain embodiments, for example, the checking the further preconfigured list may comprise matching at least a portion of a member of the further preconfigured list with a 2-tuple comprising (a) a unique identifier for the second application and the user of the second application and (b) a port number associated with the port. In certain further embodiments, for example, the port may be the destination port.

M. In certain embodiments, for example, the method may further comprise: communicating the data from a second middleware present on the second node to the second application.

Certain embodiments may provide, for example, a method for authorized network communication. In certain embodiments, for example, the method may comprise: detecting (for example receiving or intercepting) a request by a first application present on a first node (for example a computing device such as an edge device in an Internet-of-Things) to transmit data to a second application present on a second node, validating the authority of the first application to transmit the data, passing the data from the first application to a first middleware on the first node, transmitting a network packet (for example an Internet Protocol (IP) packet) containing the data through a network tunnel (for example an encrypted network tunnel), and testing the authority of the second application to receive the data.

A. In certain further embodiments, for example, the validating may be based at least on a first port number (for example a transport layer port number according to the OSI model). In certain further embodiments, for example, the first application may comprise a computer program executing on the first node and the first port number may be associated with the first application. In certain embodiments, for example, the first middleware may comprise a computer program executing on the first node and the first port number may be associated with the first middleware (for example the port number may be associated with the second middleware and may be an endpoint of the network tunnel). In certain embodiments, for example, the first port number may be predetermined prior to the initialization of the network tunnel. In certain embodiments, for example, the first port number may be assigned dynamically during initialization of the network tunnel.

B. In certain embodiments, for example, the network tunnel may extend from the first middleware to a second middleware present on the second node (for example the network tunnel may extend from a port associated with the first middleware to a different port associated with the second middleware. In certain further embodiments, for example, the network tunnel may be initialized based on the detected request (for example, the initialization may be triggered by the detected request). In certain further embodiments, for example, the initialization may be based at least on mutual authentication and authorization of the first node and the second node (for example by exchange of encrypted node identification codes).

C. In certain embodiments, for example, the testing may be based at least on a second port number and a data protocol of the data. In certain further embodiments, for example, the second port number may be associated with a computer program executing on the second node, processor, or computing device. In certain further embodiments, for example, the second port number may be associated with the second application. In certain embodiments, for example, the second port number may be associated with a second middleware (for example the port number may be associated with the second middleware and may be an endpoint of the network tunnel). In certain embodiments, for example, the second port number may be predetermined prior to the initialization of the network tunnel. In certain embodiments, for example, the second port number may be assigned dynamically during initialization of the network tunnel.

D. In certain embodiments, for example, the first node may be a first computing device. In certain embodiments, for example, the first node may comprise a first processor, a first kernel, a first network stack, a first loopback interface, a first network application programming interface of the first network stack, and a first non-transitory computer-readable storage medium. In certain embodiments, for example, the second node may comprise a second processor, a second kernel, a second network stack, and a second non-transitory computer-readable storage medium. In certain embodiments, for example, the detecting may be performed by a first execution thread being executed by the first processor and at least a portion of the testing may be performed by a second execution thread being executed by the first processor. In certain embodiments, for example, the validating may be performed by the first middleware. In certain further embodiments, for example, the validating may be performed by the first execution thread. In certain further embodiments, for example, the validating may be performed by the second execution thread. In certain embodiments, for example, execution of the first middleware may be distributed at least between the first execution thread and the second execution thread. In certain embodiments, for example, the request from the first application may be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the request from the first application may not be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the request from the first application may be passed through a shim in the first network stack to the first middleware. In certain embodiments, for example, the request from the first application may be passed from the first network application programming interface directly to the first middleware. In certain embodiments, for example, the data may be passed through the loopback interface to the first middleware. In certain embodiments, for example, the data may not be passed through the first loopback interface to the first middleware. In certain embodiments, for example, the data may be passed through a shim in the first network stack to the first middleware. In certain embodiments, for example, the data may be passed from the first network application programming interface directly to the first middleware. In certain embodiments, for example, the detecting may comprise receiving or intercepting, by the first middleware, the request. In certain embodiments, for example, the detecting may occur in the first network stack. In certain embodiments, for example, the detecting may occur in the first network application programming interface.

E. In certain embodiments, for example, at least a portion of the first middleware may comprise a kernel driver. In certain embodiments, for example, at least a portion of the first middleware may comprise a kernel module process.

F. In certain embodiments, for example, the method may further comprise: preventing the first application and the second application from associating with any socket comprising a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the first application from binding with a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the second application from binding with a physical interface. In certain embodiments, for example, the method may further comprise: preventing any port associated with the first application from binding with a physical interface, preventing any port associated with the second application from binding with a physical interface.

G. In certain embodiments, for example, the network tunnel may be encrypted. In certain further embodiments, for example, at least a portion of the network packet (for example the payload, a portion of the payload, or a metadata portion of the payload) may be encrypted using a symmetric key algorithm (for example a symmetric key algorithm such as an Advanced Encryption Standard (AES) algorithm (for example 256-bit AES). In certain further embodiments, for example, the symmetric key may be obtained by Diffie-Hellman key exchange (for example Elliptic-Curve Diffie-Hellman (ECDH) key exchange). In certain further embodiments, for example, the symmetric key may be a single-use key. In certain further embodiments, for example, the symmetric key may be obtained by rotating a key derived from ECDH key exchange.

H. In certain embodiments, for example, the data protocol may be obtained from metadata present in the network packet. In certain further embodiments, for example, the metadata may be encrypted.

I. In certain embodiments, for example, the metadata may comprise a connection state indicator for the network tunnel. In certain embodiments, for example, a connection state indicator for the network tunnel may be inserted into the metadata by the first middleware. In certain embodiments, for example, a second middleware present on the second node may determine a connection state of the network tunnel by inspecting the metadata (for example by decrypting encrypted metadata followed by parsing the metadata).

J. In certain embodiments, for example, at least a portion of the validating (for example all of the validating) may be performed by the first middleware. In certain further embodiments, for example, validating may comprise the first middleware inspecting a connection state of the network tunnel (for example checking a port state of an endpoint of the network tunnel such as a network tunnel endpoint present on the first node). In certain embodiments, for example, validating may comprise matching a 2-tuple comprising the first port number and an application identifier with a predetermined, pre-authorized 2-tuple. In certain further embodiments, for example, the application identifier may comprise an application code and an application user code. In certain embodiments, for example, the application identifier and the application user code may be constructed based on a process status command (for example the “ps” command in Linux). In certain embodiments, for example, validating may comprise matching a 3-tuple comprising the first port number, an application identifier, and an application user with a predetermined, pre-authorized 3-tuple. In certain embodiments, for example, at least a portion of the validating (for example all of the validating) may be performed by a second middleware present on the second node, processor, or computing device. In certain embodiments, for example, a first portion of the validating may be performed by the first middleware and a second portion of the validating may be performed by the second middleware.

K. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata to determine a connection state of the network tunnel. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata to verify the first application is authorized. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata to verify a user of the first application is an authorized user of the first application. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata to verify a data protocol of the data is an authorized data protocol. In certain embodiments, for example, validating may comprise the second middleware inspecting the metadata to verify a descriptor comprising at least a portion of the user of the first application, at least a portion of the first application, and at least a portion of the data protocol matches a pre-stored, pre-authorized value for the descriptor.

L. In certain further embodiments, for example, the pre-stored, pre-authorized value may be selected based on (for example the pre-stored, pre-authorized value may be indexed by) at least one port number associated with the first application. In certain further embodiments, for example, the pre-stored, pre-authorized value may be selected based on at least one port number associated with the second application. In certain further embodiments, for example, the pre-stored, pre-authorized value may be selected based on at least one port number associated with the first middleware. In certain further embodiments, for example, the pre-stored, pre-authorized value may be selected based on at least one port number associated with the second middleware (for example the port number may be associated with the second middleware and may be an endpoint of the network tunnel).

M. In certain embodiments, for example, the initializing the network tunnel may comprise obtaining the predetermined, pre-authorized 2-tuple. In certain embodiments, for example, the initializing the network tunnel may comprise obtaining the predetermined, pre-authorized 3-tuple.

N. In certain embodiments, for example, the validating may comprise the first middleware verifying (for example verifying in a kernel of the first node) that data sent from the first application is permitted to pass through a first port identified by a first port number (for example wherein the first port number is a port number associated with the first middleware). In certain further embodiments, for example, the validating may comprise a second middleware present on the second node parsing metadata present in the network packet to obtain a descriptor comprising a first application component, a first application user component, and a data protocol component. In certain further embodiments, for example, the validating may comprise the second middleware looking up a predetermined value based on a destination port number of the network packet. In certain further embodiments, for example, the validating may comprise comparing the obtained descriptor with the looked-up, predetermined value. In certain embodiments, for example, at least a portion of the testing (for example all of the testing) may be performed by a second middleware present on the second node, processor, or computing device. In certain embodiments, for example, a first portion of the testing may be performed by the first middleware and a second portion of the testing may be performed by the second middleware. In certain embodiments, for example, the testing may comprise the second middleware inspecting metadata of the network packet. In certain further embodiments, for example, the testing may comprise the second middleware parsing the metadata to obtain a connection state indicator of the network tunnel. In certain embodiments, for example, the testing may comprise the second middleware comparing a destination port number of the network packet with a predetermined, pre-authorized destination port number.

O. In certain embodiments, for example, the testing may comprise testing, by at least a portion of a second middleware present on the second node (for example at least a portion of a middleware executing in a kernel of the second node), whether a destination port of the network packet matches an open, pre-authenticated second port number. In certain embodiments, for example, the open, pre-authenticated second port number may be pre-authenticated during the initialization of the tunnel network based on (a) being associated with the second middleware; (b) appearing in a record present on the second node, the record comprising the second application, a user of the second application, and a port number associated with the second application and the user of the second application; and (c) an open connection comprising the port number associated with the second application and the user of the second application.

P. In certain embodiments, for example, the method may further comprise: communicating the data from a second middleware present on the second node to the second application.

Q. In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may be independent of initializing the network tunnel. In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may occur after the network tunnel is initialized. In certain embodiments, for example, the network tunnel may be encrypted based on executing an encryption algorithm (for example encrypted based on executing a key exchange algorithm) and the mutual authentication and authorization of the first node and the second node may be performed separately from the executing the encryption algorithm (for example may be performed after the executing the encryption algorithm). In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may comprise encrypting a first node identification code using a cryptographic key derived from the executing the key exchange algorithm. In certain further embodiments, for example, the cryptographic key may be nonpublic (for example the cryptographic key may be a shared secret between the first middleware and a second middleware executing on the second node). In certain embodiments, for example, the mutual authentication and authorization of the first node and the second node may comprise: (a) encrypting a first node identification code using a first cryptographic key derived from the executing the key exchange algorithm, and (b) encrypting a second node identification code using a second cryptographic key (for example a second cryptographic key that is different from the first cryptographic key) derived from the executing the key exchange algorithm. In certain further embodiments, for example, the cryptographic key may be nonpublic (for example the first cryptographic key and the second cryptographic key may each be a shared secret between the first middleware and a second middleware executing on the second node).

Certain embodiments may provide, for example, a method for authorized network communication, comprising: i) detecting a request by a first application present on a first node to transmit data to a second application present on a second node; ii) validating the authority of the first application to transmit the data, the validating based at least on a predetermined port number of the first application; iii) passing the data from the first application to a first middleware on the first node; iv) transmitting a network packet containing the data through a network tunnel, the network tunnel extending from the first middleware to a second middleware present on the second node, the network tunnel initialized based on the detected request, the initialization based at least on mutual authentication and authorization of the first node and the second node; and v) testing the authority of the second application to receive the data, the testing based at least on a predetermined port number of the second application and a data protocol of the data.

Certain embodiments may provide, for example, a method for authorized network communication. In certain embodiments, for example, the method may comprise detecting a request by a first application process on a first node to establish a connection for transmitting data having a data type to a second application process at a destination port number. In certain embodiments, for example, the method may comprise validating the authority of the first application process to transmit the data at least by checking a preconfigured list present on the first node for a combination of a first application process identifier and the destination port number. In certain embodiments, for example, the method may comprise passing the data from the first application process to a first middleware process on the first node, processor, or computing device. In certain embodiments, for example, the method may comprise establishing a dedicated encrypted communication pathway for transmitting data having the data type between the first application process and the second application process, the dedicated encrypted communication pathway extending from the first middleware process to a second middleware process on the second node, by mutual authentication and authorization of the first node and/or the second node, the first application process and/or the second application process, a first application process owner and/or a second application process owner, and/or a data protocol of the data.

A. In certain embodiments, for example, the data may be passed from the first application process to the first middleware process by a TCP connection. In certain embodiments, for example, the encrypted communication pathway may comprise a UDP connection. In certain embodiments, for example, the data may be passed from the first application process to the first middleware process by a TCP connection and the encrypted communication pathway may comprise a UDP connection. In certain embodiments, for example, the data may be passed from the second application process to the second middleware process by a further TCP connection. In certain embodiments, for example, the data may be passed from the first application process to the first middleware process by a TCP connection, the encrypted communication pathway may comprise a UDP connection, and the data may be passed from the second application process to the second middleware process by a further TCP connection.

Certain embodiments may provide, for example, a method for authorized network communication, comprising: i) detecting a request by a first application process on a first node to establish a connection for transmitting data having a data type to a second application process at a destination port number; ii) validating the authority of the first application process to transmit the data at least by checking a preconfigured list present on the first node for a combination of a first application process identifier and the destination port number; iii) passing the data from the first application process to a first middleware process on the first node; iv) establishing a dedicated encrypted communication pathway for transmitting data having the data type between the first application process and the second application process, the dedicated encrypted communication pathway extending from the first middleware process to a second middleware process on the second node, by mutual authentication and authorization of the first node and/or the second node, the first application process and/or the second application process, a first application process owner and/or a second application process owner, and/or a data protocol of the data.

Certain embodiments may provide, for example, plural nodes coupled to a network, wherein each data transfer between a first node of the plural nodes and a second node (for example each second node) of the plural nodes may be according to one of the foregoing methods for authorized communication. In certain further embodiments, for example, the plural nodes coupled to the network may define a software-defined network (for example plural virtual router switches cooperatively configured with one another).

Certain embodiments may provide, for example, a method to securely transport plural data packets (for example plural IP packets), comprising: configuring a data pathway from a first application (for example an application program) executing on a first node to a second application executing on a second node, and exchanging node identification codes over at least a portion of the data pathway to at least partially authorize the at least a portion of the data pathway. In certain further embodiments, for example, the method may comprise, for each one of the transported plural packets from the first application: executing operating system commands to verify that the at least partially authorized at least a portion of the data pathway remains unaltered; reading first application user and data protocol metadata to obtain at least one descriptor (for example at one 4-byte or 8-type descriptor); and comparing the at least one descriptor with members of a static list (for example a predetermined white list of authorized descriptors).

A. In certain embodiments, for example, the data pathway may transport packets exclusively between endpoints defined by the first application and the second application (for example a port associated with the first application and a port associated with the second application). In certain further embodiments, for example, the authorized at least a portion of the data pathway may transport packets exclusively on the data pathway.

B. In certain embodiments, for example, the at least a portion of the data pathway may be encrypted based on executing an encryption algorithm (for example encrypted based on executing a key exchange algorithm) and the exchanging node identification codes may be performed separately from the executing the encryption algorithm (for example may be performed after the executing the encryption algorithm). In certain embodiments, for example, the exchanging node identification codes may comprise encrypting a first node identification code using a cryptographic key derived from the executing the key exchange algorithm. In certain further embodiments, for example, the cryptographic key may be nonpublic (for example the cryptographic key may be a shared secret between the first middleware and a second middleware executing on the second node). In certain embodiments, for example, the exchanging node identification codes may comprise: (a) encrypting a first node identification code using a first cryptographic key derived from the executing the key exchange algorithm, and (b) encrypting a second node identification code using a second cryptographic key (for example a second cryptographic key that is different from the first cryptographic key) derived from the executing the key exchange algorithm. In certain further embodiments, for example, at least one of the node identification codes may be nonpublic (for example the first node identification code and the second node identification code may each be a shared secret between a network security software executing on the first node and a network security software executing on the second node).

C. In certain embodiments, for example, the method may comprise decrypting the first application user and data protocol metadata prior to the reading.

D. In certain embodiments, for example, the at least one descriptor may be an n-tuple, wherein n may be at least 2 (for example a 2-tuple). In certain embodiments, for example, the n-tuple may be an at least a 2-tuple, an at least a 3-tuple, an at least a 5-tuple, an at least a 6-tuple, an at least an 8-tuple, an at least a 10-tuple, or an at least a 12-tuple.

E. In certain embodiments, for example, the static list may be present on the second node, processor, or computing device. In certain embodiments, for example, the comparing may be performed on the second node, processor, or computing device.

F. In certain embodiments, for example, the executing operating system commands may verify that a packet originated from an authenticated, authorized process on the first node, processor, or computing device. In certain further embodiments, for example, the verifying may comprise inspecting packet metadata to confirm that a packet originated from an authorized user on the first node, processor, or computing device.

G. In certain embodiments, for example, the executing operating system commands may comprise checking a connection state of the at least partially authorized at least a portion of the data pathway. In certain further embodiments, for example, said checking may comprise parsing packet metadata. In certain further embodiments, for example, said checking may comprise comparing the parsed metadata to members of a list of connections. In certain further embodiments, for example, each member of the list of connections may comprise a connection status indicator. In certain embodiments, for example, one or more members of the list of connections may comprise a disallowed flag indicating, when the disallowed flag is set to a predetermined value, that the at least partially authorized at least a portion of the data pathway is disallowed. In certain further embodiments, for example, the method may comprise terminating the at least partially authorized at least a portion of the data pathway if the checking the connection status, based on detecting the disallowed flag, determines that the at least partially authorized at least a portion of the data pathway is disallowed. In certain embodiments, for example, the connection status of a member of the list of connections may be updated at least based on the parsed metadata. In certain further embodiments, for example, a disallowed flag of a member of the list of connections may be set at least based on the parsed metadata.

H. In certain embodiments, for example, the method may further comprise, for each one of the transported plural packets from the first application: comparing a destination port number with a white list of authorized destination port numbers.

Certain embodiments may provide, for example, a method to securely transport plural data packets, comprising: i) configuring a data pathway from a first application executing on a first node to a second application executing on a second node; ii) exchanging node identification codes over at least a portion of the data pathway to at least partially authorize the at least a portion of the data pathway; and iii) for each one of the transported plural packets from the first application: a) executing operating system commands to verify that the at least partially authorized at least a portion of the data pathway remains unaltered; b) reading first application user and data protocol metadata to obtain at least one descriptor; and c) comparing the at least one descriptor with a static list of authorized descriptors.

Certain embodiments may provide, for example, a multifactor method having overlapping security layers to securely transport plural data packets from a first application executing on a first node to a second application executing on a second node, processor, or computing device. In certain embodiments, for example, each one of the plural data packets may share a common data protocol with each other one of the plural data packets. In certain further embodiments, for example, the method may comprise: configuring a series of dedicated network tunnels, and exchanging and authorizing node identification codes over the encrypted second middleware tunnel using at least two single-use cryptographic keys to authorize the second network tunnel independently of the configuring. In certain further embodiments, for example, the series of network tunnels may comprise: a first network tunnel between a first application port associated with the first application and a first security middleware port associated with first security middleware on the first node, a second network tunnel between the first security middleware port and a second security middleware port associated with second security middleware on the second node, the second network tunnel encrypted based on shared secret cryptography, and a third network tunnel between the second security middleware port and a second application port associated with a second application on the second node, processor, or computing device. In certain further embodiments, for example, the method may comprise, for each one of the transported plural data packets arriving at the second security middleware port: executing operating system commands to verify that connection states of the series of dedicated network tunnels are unchanged, encrypting, inserting, decrypting, and reading first application user and data protocol metadata, the encrypting and decrypting each using a single-use cryptographic key, and comparing the first application user and data protocol metadata with members of a static list (for example a static list of authorized 2-tuples).

Certain embodiments may provide, for example, a multifactor method having overlapping security layers to securely transport plural data packets from a first application executing on a first node to a second application executing on a second node, each one of the plural data packets sharing a common data protocol with each other one of the plural data packets, comprising: i) configuring a series of dedicated network tunnels comprising: a) a first network tunnel between a first application port associated with the first application and a first security middleware port associated with first security middleware on the first node; b) a second network tunnel between the first security middleware port and a second security middleware port associated with second security middleware on the second node, the second network tunnel encrypted based on shared secret cryptography; and c) a third network tunnel between the second security middleware port and a second application port associated with a second application on the second node; ii) exchanging and authorizing node identification codes over the encrypted second middleware tunnel using at least two single-use cryptographic keys to authorize the second network tunnel independently of the configuring; and for each one of the transported plural data packets arriving at the second security middleware port: iii) executing operating system commands to verify that connection states of the series of dedicated network tunnels are unchanged; iv) encrypting, inserting, decrypting, and reading first application user and data protocol metadata, the encrypting and decrypting each using a single-use cryptographic key; and v) comparing the first application user and data protocol metadata with members of a static list.

Certain embodiments may provide, for example, a method to provision resources for authorized communication over a network, comprising: detecting an attempt by a first user of a first program to trigger a transmission of data from a first port on a first node to a second port on a second node, filtering the attempt to determine whether the attempt is permissible, and if the attempt is permissible, configuring a data pathway for transmitting the data, the data pathway comprising a third port and a fourth port each interposed between the first port and the second port. In certain further embodiments, for example, the filtering may be based at least on: identity of the first user, identity of the first program, and the second port.

A. In certain embodiments, for example, the attempt may comprise a connection request (for example a connection request initiated at a network application programming interface).

B. In certain embodiments, for example, the configuring may further comprise recording a connection state of at least a portion of the data pathway. In certain embodiments, for example, the configuring may further comprise recording a connection state of at least a portion of the data pathway having the third port and the fourth port as endpoints. In certain embodiments, for example, the configuring may further comprise recording a connection state of the data pathway.

C. In certain embodiments, for example, the determining may comprise comparing the attempt to a list of permissible attempts.

D. In certain embodiments, for example, at least a portion of the list of permissible attempts may be maintained on the first node solely in kernel random access memory. In certain further embodiments, for example, the at least a portion of the list of permissible attempts may comprise a list of data destination ports and, for each member of the list of destination ports, a user (for example a user of an application associated with the destination port). In certain further embodiments, for example, the at least a portion of the list of permissible attempts may comprise an application program. In certain embodiments, for example, the at least a portion of the list of permissible attempts may be accessible solely by a singular program executing in the kernel. In certain further embodiments, for example, the at least a portion of the list of permissible attempts may be loaded into the kernel random access memory of the first node from a file (for example a file resident on a non-transitory computer-readable storage medium (for example a nonvolatile memory) of the first node) solely by a different singular program.

E. In certain embodiments, for example, the file may be cryptographically signed. In certain embodiments, for example, the file may be encrypted. In certain embodiments, for example, the file may be read-only. In certain embodiments, for example, the file may be a kernel access-only file. In certain embodiments, for example, the file may be a kernel access-only file. In certain embodiments, for example, the file may not be a kernel access-only file. In certain embodiments, for example, the file may be a binary file. In certain embodiments, for example, the file may be accessible from the first node solely be a single program (for example a program executing in an OSI application layer of the first node) executing on a processor of the first node, processor, or computing device. In certain embodiments, for example, the file may be a read-only, encrypted file readable only by a single program executing on a processor of the first node, processor, or computing device.

F. In certain embodiments, for example, the first port, second port, third port, and fourth port may each be restricted to establishing no more than a single data communications session. In certain embodiments, for example, the data may pass through each port.

G. In certain embodiments, for example, the first port may be exclusively associated with a first user mode program. In certain embodiments, for example, the first port may be exclusively associated with a first application program. In certain embodiments, for example, the second port may be exclusively associated with a second user mode program. In certain embodiments, for example, the second port may be exclusively associated with a second application program. In certain embodiments, for example, the first port may be exclusively associated with a first user mode program and the second port may be exclusively associated with a second application program. In certain embodiments, for example, the first port may be exclusively associated with a first user mode program. In certain embodiments, for example, the first port may be exclusively associated with a first user mode program. In certain embodiments, for example, the second port may be exclusively associated with a second user mode program. In certain embodiments, for example, the second port may be exclusively associated with a second user mode program. In certain embodiments, for example, the first port may be exclusively associated with a first user mode program and the second port may be exclusively associated with a second user mode program.

H. In certain embodiments, for example, the data may be translated into a common format (for example a format based on MQ Telemetry Transport protocol) for transport between the third and fourth port.

Certain embodiments may provide, for example, a method of transmitting non-malicious packets of data over a network, comprising: loading data packet filters into random access memory on a first node coupled to the network, initializing a network tunnel (and/or an encrypted communication pathway) to transmit the data, assigning one of the loaded data packet filters to the network tunnel (and/or the encrypted communication pathway), passing packets of data from the transmitting application through the assigned data packet filter, encrypting at least a portion of the filtered packets, and transmitting through the network tunnel (and/or the encrypted communication pathway) only the filtered packets having at least a destination port number, a data source application, and a user of the data source application matching the assigned data packet filter.

A. In certain embodiments, for example, the data packet filter may further comprise a destination network address. In certain embodiments, for example, an encryption key used in the encrypting may be used only once. In certain embodiments, for example, initializing the network tunnel (and/or the encrypted communication pathway) may comprise shared secret cryptography. In certain embodiments, for example, the network tunnel (and/or the encrypted communication pathway) may be unidirectional. In certain embodiments, for example, the network tunnel (and/or the encrypted communication pathway) may be bidirectional. In certain embodiments, for example, each one of the data packet filters may comprise a sequential series of sub-filters.

Certain embodiments may provide, for example, a method of transmitting non-malicious packets of data over a network, comprising: loading data packet filters into random access memory on a first node coupled to the network, initializing a network tunnel (and/or an encrypted communication pathway) to receive the data, assigning one of the loaded data packet filters to the network tunnel (and/or the encrypted communication pathway), receiving packets of data from the network tunnel (and/or the encrypted communication pathway), passing the packets of data through the assigned data packet filter, and passing to an OSI application layer of the first node only the filtered packets having at least a destination port number, a data source application, a user of the data source application, and a data protocol descriptor matching the assigned data packet filter.

A. In certain embodiments, for example, filtered packets passed to the OSI application layer further may have a command type descriptor having a value and/or falling in a range specified by the assigned data packet filter. In certain embodiments, for example, filtered packets passed to the OSI application layer may further have a date and/or time falling in a range specified by the assigned data packet filter. In certain embodiments, for example, filtered packets passed to the OSI application layer further may have an expected elapse time falling in a range specified by the assigned data packet filter. In certain embodiments, for example, the data protocol descriptor may conform to an MQ Telemetry Transport protocol. In certain embodiments, for example, the data protocol descriptor may conform to a file transfer protocol. In certain embodiments, for example, the data protocol descriptor may conform to a domain name server protocol. In certain embodiments, for example, the data protocol descriptor may conform to an internet control message protocol. In certain embodiments, for example, the data protocol descriptor may conform to a structured query language protocol. In certain embodiments, for example, the data protocol descriptor may conform to a publish-subscribe messaging pattern protocol. In certain embodiments, for example, the data protocol descriptor may conform to a data distribution service protocol. In certain embodiments, for example, the data protocol descriptor may comprise a publish-subscribe topic identifier. In certain embodiments, for example, the data protocol descriptor may comprise a data structure identifier. In certain embodiments, for example, the data protocol descriptor may comprise a data type identifier. In certain embodiments, for example, the data protocol descriptor may comprise a data definition identifier.

Certain embodiments may comprise, for example, a method of transmitting non-malicious packets of data over a network. In certain embodiments, for example, the method may comprise: loading data packet filters into kernel random access memory (or in certain other embodiments, for example, loading the data packet filters in application space memory) on a first node coupled to the network, initializing a network tunnel (and/or an encrypted communication pathway) to transmit the data, assigning one of the loaded data packet filters to the network tunnel (and/or the encrypted communication pathway), passing packets of data from the transmitting application through the assigned data packet filter, encrypting at least a portion of the filtered packets, and transmitting through the network tunnel (and/or encrypted communication pathway) only the filtered packets having at least an application port number, an encrypted port number, a data protocol field, and a destination port number matching the assigned data packet filter.

A. In certain embodiments, for example, the data may be application program data. In certain embodiments, for example, the data may be a file or a portion thereof (for example an executable file). In certain embodiments, for example, an encryption key used in the encrypting may be a single-use key. In certain embodiments, for example, the encryption key may be used only once. In certain embodiments, for example, initializing the network tunnel (and/or the encrypted communication pathway) may comprise shared secret cryptography. In certain embodiments, for example, the network tunnel (and/or the encrypted communication pathway) may be unidirectional. In certain embodiments, for example, the network tunnel (and/or the encrypted communication pathway) may be bidirectional. In certain embodiments, for example, each one of the data packet filters may comprise a sequential series of sub-filters. In certain embodiments, for example, the method may further comprise: transmitting to the network only the filtered packets containing a parameter specifying a file size of a file, wherein the file size falls in a range specified by the assigned data packet filter. In certain embodiments, for example, the method may further comprise: transmitting to the network only the filtered packets containing a parameter specifying a command type, wherein the command type has a value and/or falls in a range specified by the assigned data packet filter. In certain embodiments, for example, the method may further comprise: transmitting to the network only the filtered packets containing a parameter specifying a date and/or time, wherein the specified data and/or time falls in a range specified by the assigned data packet filter. In certain embodiments, for example, the method may further comprise: transmitting to the network only the filtered packets containing a parameter specifying a an expected elapsed time, wherein the expected elapsed time falls in a range specified by the assigned data packet filter. In certain further embodiments, for example, the method may further comprise: transmitting to the network only the filtered packets having an actual and/or estimated transmission time falling in a range specified by the assigned data packet filter.

B. In certain embodiments, for example, the data protocol field may identify an MQTT protocol. In certain embodiments, for example, the data protocol field may conform to a publish-subscribe messaging pattern protocol (for example a data distribution service (DDS) protocol). In certain embodiments, for example, the data protocol field may identify a Constrained Application Protocol (CaOP). In certain embodiments, for example, the data protocol field may identify an OMA LightweightM2M (LWM2M) protocol. In certain embodiments, for example, the data protocol field may identify a JavaScript Object Notation (JSON) protocol. In certain embodiments, for example, the data protocol field may identify a Representational State Transfer (REST) protocol. In certain embodiments, for example, the data protocol field may identify an OPC Unified Architecture (OPC-UA) protocol. In certain embodiments, for example, the data protocol field may identify a file transfer protocol. In certain embodiments, for example, the data protocol field may identify a domain name server protocol. In certain embodiments, for example, the data protocol field may identify an internet control message protocol. In certain embodiments, for example, the data protocol field may identify a structured query language protocol. In certain embodiments, for example, the data protocol field may comprise a publish-subscribe topic identifier. In certain embodiments, for example, the data protocol field may comprise a data structure identifier. In certain embodiments, for example, the data protocol field may comprise a data type identifier. In certain embodiments, for example, the data protocol field may comprise a data definition identifier.

Certain embodiments may provide, for example, a network security product for managing all port-to-port communications of a networked processor node, processor, or computing device. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having a configuration file embodied therein for processing in the networked processor node by network security software to define authorized port-to-port communications. In certain embodiments, for example, the configuration file may comprise a universal nonpublic identifier for the networked processor node, processor, or computing device. In certain further embodiments, for example, the configuration file may comprise a series of records comprising parameters for authorized port-to-port communications. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise an identifier for an authorized application resident on the networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise an identifier for an authorized user associated with the authorized application resident on the networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise a universal nonpublic identifier for a remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise an identifier for an authorized application resident on the remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise an identifier for an authorized user associated with the authorized application resident on the remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise a port associated with the authorized application resident on the remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise a port associated with a network security software resident on the remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise a data protocol descriptor.

Certain embodiments may provide, for example, a network security product for managing all port-to-port communications of a networked processor node, processor, or computing device. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having a configuration file embodied therein for processing in the networked processor node by network security software to define authorized port-to-port communications. In certain embodiments, for example, the configuration file may comprise a universal nonpublic identifier for the networked processor node, processor, or computing device. In certain further embodiments, for example, the configuration file may comprise a series of records comprising parameters for authorized port-to-port communications. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise an identifier for an authorized application resident on the networked processor node, an identifier for an authorized user associated with the authorized application resident on the networked processor node, a universal nonpublic identifier for a remote networked processor node, an identifier for an authorized application resident on the remote networked processor node, an identifier for an authorized user associated with the authorized application resident on the remote networked processor node, and a data protocol descriptor. In certain further embodiments, for example, each of one or more of (for example each of) the series of records may comprise a port associated with the authorized application resident on the remote networked processor node, processor, or computing device. In certain embodiments, for example, each of one or more of (for example each of) the series of records may comprise a port associated with a network security software resident on the remote networked processor node, processor, or computing device.

Certain embodiments may provide, for example, a network security product for managing all port-to-port communications of a networked processor node, the product comprising a non-transitory computer-readable storage medium having a configuration file embodied therein for processing in the networked processor node by network security software to define authorized port-to-port communications, the configuration file comprising: i) a universal nonpublic identifier for the networked processor node; and ii) a series of records comprising parameters for authorized port-to-port communications, each of the series of records comprising at least two of the following: a) an identifier for an authorized application resident on the networked processor node; b) an identifier for an authorized user associated with the authorized application resident on the networked processor node; c) a universal nonpublic identifier for a remote networked processor node; d) an identifier for an authorized application resident on the remote networked processor node; e) an identifier for an authorized user associated with the authorized application resident on the remote networked processor node; f) optionally, a port associated with the authorized application resident on the remote networked processor node; g) optionally, a port associated with a network security software resident on the remote networked processor node; and h) optionally, a data protocol descriptor.

Certain embodiments may provide, for example, a distributed system. In certain embodiments, for example, the distributed system may comprise: plural security programs resident on computer-readable storage media of plural networked nodes, the plural security programs cooperatively configured to negotiate dedicated data pathways for port-to-port communications between the plural networked nodes. In certain embodiments, for example, the negotiating may comprise, on a first node, negotiating a first data pathway between a first user-application and a first network security program of the plural security programs. In certain embodiments, for example, the negotiating may comprise, on a second node, negotiating a second data pathway between a second network security program of the plural security programs and a second user-application. In certain embodiments, for example, the negotiating may comprise negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising a network tunnel and/or an encrypted communication pathway. In certain embodiments, for example, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

A. In certain embodiments, for example, the first data pathway and/or the second data pathway may comprise a TCP connection. In certain embodiments, for example, the third data pathway may comprise a UDP connection. In certain embodiments, for example, the first data pathway and/or the second data pathway may comprise a TCP connection, and the third data pathway may comprise a UDP connection.

Certain embodiments may provide, for example, a distributed system comprising: plural security programs resident on computer-readable storage media of plural networked nodes, the plural security programs cooperatively configured to negotiate dedicated data pathways for port-to-port communications between the plural networked nodes, the negotiating comprising: i) on a first node, negotiating a first data pathway between a first user-application and a first network security program of the plural security programs; ii) on a second node, negotiating a second data pathway between a second network security program of the plural security programs and a second user-application; and iii) negotiating a third data pathway between the first network security program and the second network security program, the third data pathway comprising a network tunnel and/or an encrypted communication pathway, each of the first data pathway, second data pathway, and third data pathway participate to form at least a part of a dedicated data pathway for exclusively communicating data from a first port of the first user-application to a second port of the second user-application.

Certain embodiments may provide, for example, a method of securing a node connected to the internet, comprising: authorizing incoming packets by comparing metadata from the packets to a list of authorized packet sources, applications, and payload protocols, and allowing only payloads from authorized packets to pass to an OSI application layer of the node, processor, or computing device. In certain further embodiments, for example, the method may be performed at a rate of at least 95% of wire speed and at most 10% processor load.

Certain embodiments may provide, for example, a method of securing a node (for example a computing device) connected to the internet. In certain embodiments, for example, the method may comprise: authorizing incoming IP packets at wire speed, allowing only payloads from authorized incoming IP packets to pass to an OSI application layer of the node, authorizing outgoing packets, allowing only authorized outgoing packets to pass to the internet. In certain further embodiments, for example, the method may be performed at a rate of at least 95% of wire speed and at most 10% processor load. In certain further embodiments, for example, the authorizing the incoming packets may comprise comparing metadata from the incoming packets to a list of authorized packet sources, applications, and payload protocols. In certain embodiments, for example, the authorizing the outgoing packets may comprise processing a list of authorized sending applications, the list containing, for each sending application present on the list of authorized sending applications, a port associated with the sending application.

A. In certain embodiments, for example, one of the foregoing methods to secure may induce a processor load of less than 5% according to the Load Benchmark Test.

B. In certain embodiments, for example, one of the foregoing methods to secure may slow network packet processing by less than 2 ms according to the Speed Benchmark Test. In certain embodiments, for example, one of the foregoing methods to secure may process at least 50,000 packets per second according to the Packet Processing Benchmark Test. In certain embodiments, for example, one of the foregoing methods to secure may prevent the secure node from establishing data communications sessions if greater than 90% of random access memory is utilized. In certain embodiments, for example, one of the foregoing methods to secure may be further configured to terminate all secure node data communications sessions if greater than 99% of random access memory is utilized. In certain embodiments, for example, the metadata may be obtained from a predetermined portion of each packet. In certain embodiments, for example, the rate and processor load of one of the foregoing methods to secure may be measured based on an Ethernet port having at least a 1 Gigabit (Gb) bandwidth (for example a 10 Gb bandwidth) and having less than 10% overhead. In certain embodiments, for example, the processor load may be based on a 1 GHz ARM9 processor running Microlinux.

Certain embodiments may provide, for example, a method of securing a computing device connected to the internet, comprising: i) authorizing incoming packets, at wire speed, by comparing metadata from the incoming packets to a list of authorized packet sources, applications, and payload protocols; ii) allowing only payloads from authorized incoming packets to pass to the OSI application layer of the node; iii) authorizing outgoing packets, based on a list of authorized source ports and sending applications; and iv) allowing only authorized outgoing packets to pass to the internet, at a rate of at least 95% of wire speed and at most 10% processor load.

Certain embodiments may provide, for example, a secure node comprising a processor, random access memory, and network security software, the network security software configured to: match, in a kernel of the secure node (or, in certain other embodiments, for example, an application space of the secure node), a destination port number of each incoming network packet to a member of a list of authorized destination ports, decrypt metadata from each incoming network packet, and compare the decrypted metadata to a list of authorized n-tuples (for example at least 2-tuples, an at least 3-tuples, at least 5-tuples, at least 6-tuples, at least 8-tuples, at least 10-tuples, or at least 12-tuples), each n-tuples in the list of authorized n-tuples comprising descriptors for: a packet payload source application and a payload protocol. In certain further embodiments, for example, the matching, decrypting, and comparing may be performed at a rate of at least 95% of wire speed and at most 10% processor load based on a 1 Gb Ethernet port having less than 10% overhead.

A. In certain embodiments, for example, the network security software may induce a processor load of less than 5% according to the Load Benchmark Test. In certain embodiments, for example, the network security software may slow network packet processing by less than 2 ms according to the Speed Benchmark Test. In certain embodiments, for example, the node may process at least 50,000 packets per second according to the Packet Processing Benchmark Test. In certain embodiments, for example, the network security software may be further configured to prevent the secure node from establishing data communications sessions if greater than 90% of random access memory is utilized. In certain embodiments, for example, the network security software may be further configured to terminate all secure node data communications sessions if greater than 99% of random access memory is utilized. In certain embodiments, for example, packet payload source application descriptor may comprise an application identifier and a user identifier. In certain embodiments, for example, the metadata may be obtained from a predetermined portion of each packet.

B. In certain embodiments, for example, the processor load may be based on an Ethernet port having at least a 1 Gigabit (Gb) bandwidth (for example a 10 Gb bandwidth) and having less than 10% overhead. In certain embodiments, for example, the processor load may be based on a 1 GHz ARM9 processor running Microlinux. In certain embodiments, for example, the metadata may be decrypted using a symmetric decryption algorithm (for example 256-bit AES). In certain further embodiments, for example, the decrypting may comprise using a cryptographic key (for example a cryptographic key derived from Elliptic-Curve Diffie-Hellman (ECDH) key exchange. In certain further embodiments, for example, the key may be a single-use key. In certain embodiments, for example, the key may be a rotated key.

C. In certain embodiments, for example, the network security software may be configured to drop (or discard) an incoming network packet if a destination port number of the network packet is not present on the list of authorized destination ports.

D. In certain further embodiments, for example, the matching may further comprise checking a connection state associated with the destination port number. In certain embodiments, for example, the network security software may be configured to drop an incoming network packet based on a status of a connection state associated with a destination port of the network packet (for example if the connection state is not open).

E. In certain embodiments, for example, the decrypting and comparing may be performed in an OSI application layer of the secure node, processor, or computing device.

F. In certain embodiments, for example, the list of sending applications and authorized ports may comprise a security middleware application having a root user and a port associated with the security middleware application. In certain embodiments, for example, the list of sending applications and authorized ports may comprise an application program and a port associated with the application program.

Certain embodiments may provide, for example, a node preconfigured to constrain communication over a network, comprising: a file stored on non-transitory computer-readable storage medium, the file defining a list of authorized data communications sessions, each record of the file comprising. In certain further embodiments, for example, each record of the file may further comprise: a) a universal identifier for a data source, comprising an authorized source application identifier and an identifier for an authorized user of the source application; b) a universal identifier for a data destination, comprising an authorized destination application identifier and an identifier for an authorized user of the destination application; c) a port associated with the destination application; d) a different port associated with a middleware; and e) a data protocol field.

A. In certain embodiments, for example, the file may be a binary file. In certain embodiments, for example, the file may be a variable record length file. In certain embodiments, for example, the file may be encrypted on the non-transitory computer-readable storage medium. In certain embodiments, for example, the port associated with the destination application may communicate with the middleware by a loopback interface. In certain embodiments, for example, the different port associated with the middleware may be an endpoint of an encrypted tunnel-portion of an authorized data communications session of the authorized data communications sessions. In certain embodiments, for example, each record of the file may comprise a network interface controller code for a network interface controller present on the node, processor, or computing device. In certain further embodiments, for example, a network address of the network interface controller may be determined based at least in part on the network interface controller code. In certain embodiments, for example, each record of the file may further comprise a different network interface controller code for a network interface controller present on a remote node, processor, or computing device. In certain further embodiments, for example, a network address of the remote network interface controller may be determined based at least in part on the different network interface controller code. In certain embodiments, for example, each record of the file may comprise a nonpublic identification code for the node, processor, or computing device. In certain embodiments, for example, each record of the file may comprise a nonpublic identification code for a remote node, processor, or computing device.

B. In certain embodiments, for example, each record of the file may comprise a private key (or a cryptographic parameter or primitive). In certain further embodiments, for example, the private key may be used by a key exchange algorithm executing on a processor of the node to establish a shared key with a remote node, processor, or computing device. In certain embodiments, each record of the file has a different private key.

C. In certain embodiments, for example, a portion of the file may be read into kernel random access memory on boot-up of the node, processor, or computing device. In certain embodiments, for example, the file may be accessible only by a kernel of the node, processor, or computing device. In certain embodiments, for example, the file may be accessible only by a root user of the node, processor, or computing device. In certain embodiments, for example, the file may be accessible by an application program module executed by a root user.

Certain embodiments may provide, for example, a node preconfigured to constrain communication over a network, comprising: a file stored on non-transitory computer-readable storage medium, the file defining a list of authorized data communications sessions, each record of the file comprising: a) a universal identifier for a data source, comprising an authorized source application identifier and an identifier for an authorized user of the source application; b) a universal identifier for a data destination, comprising an authorized destination application identifier and an identifier for an authorized user of the destination application; c) a port associated with the destination application; d) a different port associated with a middleware; e) a data protocol field; f) a network interface controller code for a network interface controller present on the node; g) a different network interface controller code for a network interface controller present on a remote node; h) a nonpublic identification code for the node; i) a different nonpublic identification code for the remote node; and j) a private key provisioned for use by a key exchange algorithm executing on the node to establish a shared key with the remote node, processor, or computing device.

Certain embodiments may provide, for example, a node preconfigured to constrain communication over a network, comprising a file stored on non-transitory computer-readable storage medium, the file having a list of authorized data communications sessions. In certain further embodiments, for example, each member of the list may comprise: an index defined by an application authorized to be executed on the processor and an authorized user of the application, a unique 2-tuple consisting of a port number assigned to the application and a port number assigned to a network security middleware, a unique 2-tuple consisting of a port number assigned to a remote application and a port number assigned to a remote network security middleware, and a data protocol descriptor.

A. In certain embodiments, for example, the file may be read-only. In certain embodiments, for example, the file may be cryptographically signed. In certain embodiments, for example, the read-only file may be encrypted. In certain embodiments, for example, the read-only file may be a binary file. In certain embodiments, for example, one member of the list may have a different record length than another member of the list.

B. In certain embodiments, for example, the index of a member of the list may be derived from a concatenation of a user name (or a portion thereof) and an application name (or a portion thereof), or at least portions thereof.

C. In certain embodiments, for example, the port number assigned to the application may appear only once in the list. In certain embodiments, for example, the port number assigned to the network security middleware may appear only once in the list. In certain embodiments, for example, the port number assigned to a remote application appears only once in the list. In certain embodiments, for example, the port number assigned to the remote network security middleware appears only once in the list. In certain embodiments, for example, each of the port number assigned to the application, port number assigned to the network security middleware, port number assigned to a remote application, and the remote network security middleware may appear only once in the list. In certain embodiments, for example, the data protocol descriptor may appear in a plurality of members of the list.

Certain embodiments may provide, for example, a node preconfigured to constrain communication over a network, comprising: a processor, a non-transitory computer-readable storage medium, and a read-only file stored on the non-transitory computer-readable storage medium. In certain further embodiments, for example, the file may comprise plural n-tuples, the plural n-tuples defining an exclusive list of authorized data communications sessions. In certain further embodiments, for example, each one of the plural n-tuples may comprise: an index defined by an application authorized to be executed on the processor and an authorized user of the application, a unique 2-tuple consisting of a port number assigned to the application and a port number assigned to a network security middleware, a unique 2-tuple consisting of a port number assigned to a remote application and a port number assigned to a remote network security middleware, and a data protocol descriptor.

A. In certain embodiments, for example, the network security middleware may be stored on the non-transitory computer-readable storage medium.

B. In certain embodiments, for example, the remote application and the remote network security middleware may reside on a common remote node, processor, or computing device. In certain embodiments, for example, the remote application and the remote network security middleware may reside on separate remote nodes. In certain further embodiments, for example, the remote network security middleware may reside on a software-defined perimeter controller.

C. In certain embodiments, for example, the read-only file may be cryptographically signed. In certain embodiments, for example, the read-only file may be encrypted. In certain embodiments, for example, the read-only file may be a binary file. In certain embodiments, for example, one of the n-tuples may have a different record length than another one of the n-tuples.

D. In certain embodiments, for example, the node may further comprise: network security software stored on the non-transitory computer-readable storage medium different from the network security middleware, the different network security software having sole permission to read the file. In certain further embodiments, for example, the different network security software may be configured to be executed by the processor to load at least a portion of the file into the kernel random access memory. In certain embodiments, for example, the different network security software may be executed in an OSI application layer of the node, processor, or computing device. In certain embodiments, for example, the different network security software may be executed in a kernel of the node, processor, or computing device. In certain further embodiments, for example, the at least a portion of the file may be loaded solely upon boot-up of the node, processor, or computing device.

E. In certain embodiments, for example, the network security middleware may be configured to be executed by the processor to prevent initialization of any data communications session except for the list of authorized data communications sessions.

Certain embodiments may provide, for example, a node preconfigured to constrain communication over a network, comprising: i) a processor; ii) a non-transitory computer-readable storage medium; iii) a read-only file stored on the non-transitory computer-readable storage medium, the file comprising plural n-tuples, the plural n-tuples defining an exclusive list of authorized data communications sessions, each one of the plural n-tuples comprising: a) an index defined by an application authorized to be executed on the processor and an authorized user of the application; b) a unique 2-tuple consisting of a port number assigned to the application and a port number assigned to a network security middleware, the network security middleware stored on the non-transitory computer-readable storage medium; c) a unique 2-tuple consisting of a port number assigned to a remote application and a port number assigned to a remote network security middleware; and d) a data protocol descriptor.

Certain embodiments may provide, for example, a method to retrofit a computing device coupled to a network. In certain embodiments, for example, the method may comprise: storing an encrypted file on a non-transitory computer-readable storage medium of the computing device, installing network security software on the non-transitory computer-readable storage medium of the computing device, setting permissions of the file whereby the file is readable only by the network security software; and modifying a network stack resident on the computing device to receive or intercept each data packet incoming from or outgoing to the network. In certain further embodiments, for example, the file may comprise a list interpretable by the network security middleware to define authorized communication sessions and an authorized data protocol for each authorized communication session of the authorized communication sessions. In certain further embodiments, for example, the network security software may be configured to load at least a portion of the file into kernel random access memory upon boot-up of the computing device. In certain further embodiments, for example, the network stack may be modified to route each received or intercepted data packet through the network security middleware. In certain further embodiments, for example, the network security middleware may be configured to drop a received or an intercepted data packet unless the received or intercepted data packet is authorized to be transmitted using one of the authorized communication sessions.

A. In certain embodiments, for example, the method may be exclusive of any modification to a pre-existing application program. In certain embodiments, for example, the modifying a network stack may comprise modifying a network protocol application programming interface. In certain embodiments, for example, the method may further comprise: installing cryptographic primitives (for example cryptographic primitives provided by Secured Socket Layer (SSL) software) to enable a separate encrypted network tunnel to be established for each authorized communication session of the authorized communication sessions.

Certain embodiments may provide, for example, a method to retrofit a computing device coupled to a network, comprising: i) storing an encrypted file on a non-transitory computer-readable storage medium of the computing device, the file comprising a list interpretable by network security middleware executing on the computing device to define authorized communication sessions and an authorized data protocol for each authorized communication session of the authorized communication sessions; ii) installing the network security software on the non-transitory computer-readable storage medium of the computing device, the network security software configured to load at least a portion of the file into kernel random access memory (or, in certain other embodiments, for example, into application space memory) upon boot-up of the computing device; iii) setting permissions of the file whereby the file is readable only by the network security software; and iv) modifying a network stack resident on the computing device to: a) receive or intercept each data packet incoming from or outgoing to the network; and b) route each received or intercepted data packet through the executing network security middleware, the network security middleware configured to drop a received or an intercepted data packet unless it is authorized to be transmitted using one of the authorized communication sessions.

Certain embodiments may provide, for example, a secure system. In certain embodiments, for example, the secure system may comprise: a network configured to transmit data based on at least one network packet-based protocol, and plural nodes coupled to the network, each one of the plural nodes comprising a network stack, a network protocol application programming interface, and middleware. In certain further embodiments, for example, the network protocol application programming interface may be configured to pass each data packet received to the middleware. In certain further embodiments, for example, the middleware may be configured to verify, prior to sending data towards a destination port, that the data: has been generated by an authorized application, conforms to an authorized data protocol, has been received from an authorized node, contains at least one port number that is present on a predetermined list of port numbers.

A. In certain embodiments, for example, the middleware may obtain data from a data packet passing through the network stack. In certain embodiments, for example, the data packet may be encrypted. In certain embodiments, for example, the middleware may generate metadata, encrypt metadata, and insert metadata into a partially assembled network packet.

B. In certain embodiments, for example, the at least one network packet-based protocol may comprise Ethernet protocol. In certain embodiments, for example, the at least one network packet-based protocol may comprise Wi-Fi protocol. In certain embodiments, for example, the at least one network packet-based protocol may comprise Bluetooth protocol.

C. In certain embodiments, for example, the at least one port number may be associated with an application responsible for producing a data packet. In certain embodiments, for example, the at least one port number may be associated with source port (for example may be a source port) in a network packet header. In certain embodiments, for example, the at least one port number may be associated with a destination port (for example may be a destination port) in a network packet header.

Certain embodiments may provide, for example, a secure system, comprising: i) a network configured to transmit data based on at least one network packet-based protocol; and ii) plural nodes coupled to the network, each one of the plural nodes comprising a network stack, a network protocol application programming interface, and middleware, the network protocol application programming interface configured to pass each data packet received to the middleware, the middleware configured to verify, prior to sending data towards a destination port, that the data: a) has been generated by an authorized application; b) conforms to an authorized data protocol; c) has been received from an authorized node; and d) contains at least one port number that is present on a predetermined list of port numbers.

Certain embodiments may provide, for example, a secure system, comprising: i) a network configured to transmit data based on at least one network packet-based protocol; and ii) plural nodes coupled to the network, each one of the plural nodes comprising a network stack, a network protocol application programming interface, and a middleware, invocation of the middleware being triggered by each data packet crossing the network protocol application programming interface for the first time, the middleware configured to verify, prior to sending data towards a destination port, that the data: a) has been generated by an authorized application, as determined based at least on metadata obtained by the middleware; b) conforms to an authorized data protocol, as determined based at least on the metadata; c) has been received from an authorized node; and d) contains at least one port number that is present on a predetermined list of port numbers.

Certain embodiments may provide, for example, a distributed method to secure plural computing devices coupled to a network. In certain embodiments, for example, the distributed method may comprise: having preprovisioned (or predetermined) configuration files on the plural computing devices, defining authorized port-to-port connections based in part on information from the configuration files on at least two of the plural computing devices (for example a first configuration file on a first computing device and a second configuration file on a second computing device), and restricting network communications to and from the plural computing devices to the authorized port-to-port connections.

A. In certain embodiments, for example, the preprovisioned (or predetermined) configuration files may be read on boot-up. In certain embodiments, for example, the preprovisioned (or predetermined) configuration files may be read by one or more application space programs. In certain embodiments, for example, the preprovisioned (or predetermined) configuration files may be read by one or more kernel space programs. In certain embodiments, for example, the preprovisioned (or predetermined) configuration files may be read by a combination of application space programs and kernel space programs.

B. In certain embodiments, for example, each one of the authorized port-to-port connections may comprise: a first socket referenced by first network security software executing on a first computing device of the plural computing devices; and a second socket referenced by network security software. In certain further embodiments, for example, the network security software may execute on: a second computing device of the plural computing devices, a third computing device executing an authorized deployment server, the authorized deployment server exclusively responsible for managing the static, preconfigured list of authorized pathways, or a fourth computing device executing a gateway server, network communication of the gateway server restricted to the authorized pathways. In certain embodiments, for example, data may be passed to the gateway server and processed by network security software on the fourth computing device unless the data is received from one of the authorized pathways. In certain embodiments, for example, the fourth computing device may be constrained, by an operating system, to executing only a static, preconfigured list of computer programs. In certain embodiments, for example, one or more of the preprovisioned (or predetermined) configuration files may be distributed by the authorized deployment server to at least two of the plural computing devices.

C. In certain embodiments, for example, the plural computing devices may be physically located at a common facility (for example a hospital, factory, chemical processing facility, power station, or offshore platform).

D. In certain embodiments, for example, at least one (for example each one) of the authorized port-to-port connections may be stateful. In certain embodiments, for example, at least one (for example each one) of the authorized port-to-port connections may be stateless.

Certain embodiments may provide, for example, a secured system comprising: plural nodes coupled to a network, and plural security programs for management of all communication between the plural nodes over the network, the plural security programs cooperatively configured to form dedicated data pathways for inter-application communication between the plural nodes. In certain further embodiments, for example, at least one of the dedicated data pathways may comprise: a first security program to send data from a first one of the plural nodes and a second security program to receive data on a second one of the plural nodes, and a dedicated encrypted network tunnel between the first security program and a second security program.

A. In certain embodiments, for example, the network may be a packet-switched network. In certain embodiments, for example, the received data may comprise a series of data packets. In certain embodiments, for example, the first security program may verify that each data packet of the series of data packets was transmitted from an authorized application. In certain embodiments, for example, the first security program may verify that a data packet of the series of data packets was transmitted from a port associated with an application authorized to transmit the data packet, based at least on a port number associated with the transmitting application, an identifier for the transmitting application, a user of the transmitting application, and a data protocol descriptor for the data packet. In certain embodiments, for example, the second security program may verify that each data packet of the series of data packets was transmitted from an authorized application. In certain embodiments, for example, the second security program may verify that each data packet of the series of data packets is being transmitted to an authorized port associated with an authorized application. In certain embodiments, for example, the second security program may verify that a data packet of the series of data packets is being transmitted to a port associated with an application authorized to receive the data packet, based at least on an identifier for the receiving application, an identifier for an application associated with the transmission of the data packet, a user of the transmitting application, and a data protocol descriptor for the data packet.

Certain embodiments may provide, for example, a secured system comprising: plural nodes coupled to a network, a first application program executing on a first node and a second application program executing on a second node, plural security programs for management of all communication between the plural nodes over the network, and plural read-only configuration files accessible by the plural security programs. In certain embodiments, for example, the plural security programs may be cooperatively configured to form a dedicated data pathway for inter-application communication between the first application program and the second application program. In certain further embodiments, for example, the dedicated data pathway may pass through a first security program and a second security program of the plural security programs, the first security program and a second security program interposed between the first application program and the second application program, and the data pathway may comprise a dedicated encrypted network tunnel between the first security program and a second security program. In certain further embodiments, for example, each of the plural configuration files may define an exclusive list of authorized inter-application communications, may further define an exclusive data protocol for each authorized inter-application communication of the exclusive list of authorized inter-application communications, may assigning a fixed port number to the first security software, and may contain nonpublic node identification codes.

A. In certain embodiments, for example, the fixed port number may be unique to a 5-tuple consisting of: an identifier for the first application program, a user of the first application program, an identifier for the second application program, a user of the second application program, and the exclusive data protocol. In certain embodiments, for example, the fixed port number may be unique on the first node and the second node to a 5-tuple consisting of: an identifier for the first application program, a user of the first application program, an identifier for the second application program, a user of the second application program, and the exclusive data protocol.

B. In certain embodiments, for example, each of the plural configuration files may be a binary file. In certain embodiments, for example, each of the plural configuration files may be divided into records. In certain further embodiments, for example, the records may be indexed by the fixed port number.

C. In certain embodiments, for example, each of the records may have a variable length. In certain embodiments, for example, each of the records may comprise a private key (or a cryptographic parameter or primitive). In certain embodiments, for example, each private key may be unique to the secured system.

D. In certain embodiments, for example, the nonpublic node identification codes may comprise a first node identification code assigned to the first node and a second node identification code assigned to the second node, processor, or computing device.

Certain embodiments may provide, for example, a secured system comprising: i) plural nodes coupled to a network; ii) a first application program executing on a first node and a second application program executing on a second node; iii) plural security programs for management of all communication between the plural nodes over the network, the plural security programs cooperatively configured to form a dedicated data pathway for inter-application communication between the first application program and the second application program, wherein the dedicated data pathway—a) passes through a first security program and a second security program of the plural security programs, the first security program and a second security program interposed between the first application program and the second application program; and b) comprises a dedicated encrypted network tunnel between the first security program and a second security program; iv) plural read-only configuration files accessible by the plural security programs, each of the plural configuration files—a) defining an exclusive list of authorized inter-application communications; b) further defining an exclusive data protocol for each authorized inter-application communication of the exclusive list of authorized inter-application communications; c) assigning a fixed port number to the first security software; and d) containing nonpublic node identification codes.

Certain embodiments may provide, for example, a secure system comprising: plural nodes configured to communicate over a network exclusively by plural encrypted communication pathways (for example by plural encrypted network tunnels), each one of the plural encrypted communication pathways (for example each one of the network tunnels) restricted to transmitting data sent from a single transmitting application on a first node of the plural nodes and directed to a single receiving application on a second node of the plural nodes. In certain further embodiments, for example, each one of the plural encrypted communication pathways (for example the plural encrypted network tunnels) may be restricted to transmitting data having a single payload data type, and encrypted with a cryptographic key that may be used only once. In certain further embodiments, for example, each one of the plural encrypted communication pathways (for example each one of the plural encrypted network tunnels) may be established by mutual exchange and authentication of preconfigured application authentication identification codes and nonpublic node identification codes. In each of the foregoing embodiments, the transmitting application, first node, receiving application, and/or receiving node may be different for each different encrypted network communication (for example each different network tunnel) of the plural encrypted network communication pathways (for example of the plural encrypted network tunnels).

A. In certain embodiments, for example, the plural encrypted communication pathways (for example the plural encrypted network tunnels) may comprise one or plural unidirectional encrypted communication pathways (for example one or plural unidirectional encrypted network tunnels). In certain embodiments, for example, the plural encrypted communication pathways (for example the plural encrypted network tunnels) may comprise one or plural bidirectional encrypted communication pathways (for example one or plural bidirectional network tunnels).

B. In certain embodiments, for example, the plural encrypted communication pathways (for example the plural encrypted network tunnels) may comprise one or plural stateful data communications sessions. In certain embodiments, for example, the plural encrypted communication pathways (for example the plural encrypted network tunnels) may be at least partially managed by middleware present on the plural nodes. In certain embodiments, for example, the plural encrypted communication pathways (for example the plural encrypted network tunnels) may be at least partially managed by a broker software present on at least one node of the plural nodes.

Certain embodiments may provide, for example, a secure system comprising: plural nodes configured to communicate over a network exclusively by plural encrypted network tunnels, each one of the plural encrypted network tunnels—i) restricted to transmitting data—a) sent from a single transmitting application on a first node of the plural nodes; b) directed to a single receiving application on a second node of the plural nodes; c) having a single payload data type; and d) encrypted with a cryptographic key that is used only once; and ii) established by mutual exchange and authentication of preconfigured—a) application authentication identification codes; and b) nonpublic node identification codes.

Certain embodiments may provide, for example, a secure system, comprising: plural nodes coupled to a network, plural application software executing on at least a first node and a second node of the plural nodes, at least one encrypted network tunnel configured to perform at least a partial data pathway for transport of data from a first application software of the plural application software on the first node of the plural nodes to a second application software of the plural application software on the second node of the plural nodes, the data conforming to a preconfigured, predefined, pre-established and/or preprovisioned first data protocol, and at least one security software initiating the at least one encrypted network tunnel. In certain further embodiments, for example, the at least one security software may be configured to authorize the encrypted network tunnel, based at least on authorizing the first node, the second node, the first application software, and the second application software. In certain further embodiments, for example, the at least one security software may be configured to confirm that the first application software is authorized to transmit the first data protocol. In certain further embodiments, for example, the at least one security software may be positioned between the first application software and the second application software in a data pathway comprising the at least one encrypted network tunnel.

A. In certain embodiments, for example, the encrypted tunnel may have an endpoint at a port associated with one of the at least one security software.

B. In certain embodiments, for example, the at least one security software may be plural security software, and the encrypted tunnel may have a first endpoint at a first port associated with a first security software of the plural security software and a second endpoint at a second port associated with a second security software of the plural security software.

C. In certain embodiments, for example, authorizing the first application software may comprise authorizing a user of the first application software. In certain embodiments, for example, the at least one security software may be transparent to the first application software and the second application software. In certain embodiments, for example, the authorizing and the confirming may each comprise encrypted communication over the network. In certain embodiments, for example, the system may be configured as a software-defined perimeter. In certain embodiments, for example, an access controller of the software-defined perimeter may comprise one of the at least one security software.

Certain embodiments may provide, for example, a secure system, comprising: i) plural nodes coupled to a network; ii) plural application software executing on at least a first node and a second node of the plural nodes; iii) at least one encrypted network tunnel configured to perform at least a partial data pathway for transport of data from a first application software of the plural application software on the first node of the plural nodes to a second application software of the plural application software on the second node of the plural nodes, the data conforming to a preconfigured, predefined, pre-established and/or preprovisioned first data protocol; and iv) at least one middleware initiating the at least one encrypted network tunnel, the at least one middleware positioned between the first application software and the second application software in a data pathway comprising the at least one encrypted network tunnel, the at least one middleware configured to: a) authorize the encrypted network tunnel, based at least on authorizing the first node, the second node, the first application software, and the second application software; and b) confirm that the first application software is authorized to transmit the first data protocol.

Certain embodiments may provide, for example, a secure system comprising: plural nodes coupled to a network, plural application software executing on at least a first node and a second node of the plural nodes, at least one encrypted network tunnel established between a first application software of the plural application software on the first node of the plural nodes and a second application software of the plural application software on the second node of the plural nodes, the first application software configured to send data conforming to a preconfigured, predefined, pre-established and/or preprovisioned first data protocol, and at least one middleware initiating the at least one encrypted network tunnel. In certain further embodiments, for example, the at least one middleware may be positioned between the first application software and the second application software in a data pathway comprising the at least one encrypted network tunnel. In certain further embodiments, for example, the at least one middleware may be configured to authorize the encrypted network tunnel, based at least on authorizing at least one of the plural nodes, the first application software, and the second application software. In certain further embodiments, for example, the at least one middleware may be configured to confirm that the second application software is authorized to receive the first data protocol.

A. In certain embodiments, for example, the at least one middleware may be transparent to the first application software and the second application software. In certain embodiments, for example, the authorize and the confirm may each comprise encrypted communication over the network.

Certain embodiments may provide, for example, a secure system comprising: i) plural nodes coupled to a network; ii) plural application software executing on at least a first node and a second node of the plural nodes; iii) at least one encrypted network tunnel established between a first application software of the plural application software on the first node of the plural nodes and a second application software of the plural application software on the second node of the plural nodes, the first application software configured to send data conforming to a preconfigured, predefined, pre-established and/or preprovisioned first data protocol; and iv) at least one middleware initiating the at least one encrypted network tunnel, the at least one middleware positioned between the first application software and the second application software in a data pathway comprising the at least one encrypted network tunnel, the at least one middleware configured to: a) authorize the encrypted network tunnel, based at least on authorizing at least one of the plural nodes, the first application software, and the second application software; and b) confirm that the second application software is authorized to receive the first data protocol.

Certain embodiments may provide, for example, a secure system comprising plural nodes communicating over a network by machine-to-machine middleware, each node of the plural nodes comprising: a preconfigured list, and machine-to-machine middleware. In certain embodiments, for example, each member of the preconfigured list may comprise a 2-tuple, the 2-tuple comprising a port number. In certain further embodiments, for example, the machine-to-machine middleware may be configured to: interpret the preconfigured list to define authorized client-server connections, receive a network packet from the network, decrypt an encrypted metadata portion of the network packet using a single-use cryptographic key, extract an authorization parameter from the decrypted metadata portion of the network packet, and compare a 2-tuple consisting of the destination port number of the network packet and the authorization parameter with at least one member of the preconfigured list.

A. In certain embodiments, for example, the preconfigured file may be stored on a non-transitory computer-readable storage medium (for example a nonvolatile memory storage medium) exclusively as an encrypted binary file. In certain embodiments, for example, the authorization parameter may be a remote node identification code. In certain embodiments, for example, the remote node identification code may be nonpublic. In certain embodiments, for example, the remote node identification code may be a shared secret among a subset of the plural nodes.

B. In certain embodiments, for example, the authorization parameter may comprise a remote descriptor, the remote descriptor comprising a remote application identifier, an identifier for a user of the remote application, and a data protocol code. In certain embodiments, for example, the machine-to-machine middleware may be at least partially embedded in a kernel.

Certain embodiments may provide, for example, a secure system comprising plural nodes communicating over a network by machine-to-machine middleware, each node of the plural nodes comprising: i) a preconfigured list, each member of the preconfigured list comprising a 2-tuple, the 2-tuple comprising a port number; and ii) machine-to-machine middleware configured to: a) interpret the preconfigured list to define authorized client-server connections; b) receive a network packet from the network; c) decrypt an encrypted metadata portion of the network packet using a single-use cryptographic key; d) extract an authorization parameter from the decrypted metadata portion of the network packet; and e) compare a 2-tuple consisting of the destination port number of the network packet and the authorization parameter with at least one member of the preconfigured list.

A. In certain embodiments, for example, the machine-to-machine middleware may be transparent to the client application. In certain embodiments, for example, the network packet may comprise a segmented payload. In certain embodiments, for example, at least 25% (for example at least 50%, such as at least 75%) of the plural nodes may be dedicated computing devices.

Certain embodiments may provide, for example, a secure system comprising plural nodes communicating over a network by machine-to-machine middleware, each node of the plural nodes comprising: a client application, a preconfigured list, a security layer, a kernel, and machine-to-machine middleware at least partially embedded in the kernel. In certain further embodiments, for example, the machine-to-machine middleware may be configured to: interpret the preconfigured list to define authorized client-server connections, receive a network packet from the network, decrypt an encrypted metadata portion of the network packet using a single-use cryptographic key (for example a rotated key derived from ECDH key exchange), extract at least a 2-tuple consisting of a remote server code and a data protocol code from the decrypted metadata portion of the network packet, and compare the 2-tuple to at least one member of the preconfigured list. In certain further embodiments, for example, each member of the preconfigured list may consist of an n-tuple, the n-tuple comprising a 2-tuple consisting of a remote server code and a data protocol code.

A. In certain embodiments, for example, the machine-to-machine middleware may be transparent to the client application. In certain embodiments, for example, the network packet may comprise a segmented payload. In certain embodiments, for example, at least 25% (for example at least 50%, such as at least 75%) of the plural nodes may be dedicated computing devices.

Certain embodiments may provide, for example, a secure system comprising plural nodes communicating over a network by machine-to-machine middleware, each node of the plural nodes comprising: i) a client application; ii) a preconfigured list, each member of the preconfigured list consisting of an n-tuple, the n-tuple comprising a 2-tuple consisting of a remote server code and a data protocol code; iii) a security layer; iv) a kernel; and v) machine-to-machine middleware at least partially embedded in the kernel, the machine-to-machine middleware configured to: a) interpret the preconfigured list to define authorized client-server connections; b) receive a network packet from the network; c) decrypt an encrypted metadata portion of the network packet using a single-use cryptographic key; d) extract at least a 2-tuple consisting of a remote server code and a data protocol code from the decrypted metadata portion of the network packet; and e) compare the 2-tuple to at least one member of the preconfigured list.

Certain embodiments may provide, for example, a method to instantiate and manage a dedicated data pathway extending from a source port on a first node to a destination port on a second node, processor, or computing device. In certain embodiments, for example, the method may comprise selecting, from a predetermined, exclusive list of authorized data pathways, a security port number exclusively paired with a port number of the destination port. In certain embodiments, for example, the method may comprise forming an encrypted communication pathway extending from the first node to a security port present on the second node, the security port having the selected security port number (i.e., the selected security port number assigned to the security port). In certain embodiments, for example, the method may comprise, prior to transmitting any data from the source port to the destination port: verifying, at the first node, that a first n-tuple (for example the first n-tuple may be an at least a 2-tuple, an at least a 3-tuple, an at least a 5-tuple, an at least a 6-tuple, an at least an 8-tuple, an at least a 10-tuple, or an at least a 12-tuple) received from the encrypted communication pathway matches an expected value based on the security port number, the first n-tuple comprising: a nonpublic device code for the second node, a user associated with the destination port, an application associated with the destination port, and a data protocol descriptor. In certain embodiments, for example, the method may comprise, prior to passing a network packet to the destination port: verifying, at the second node, that an second n-tuple obtained from the network packet matches an expected value based on the security port number, the second n-tuple comprising: a user associated with the source port, an application associated with the source port, and the data protocol descriptor.

Certain embodiments may comprise, for example, a method to instantiate and manage a dedicated data pathway extending from a source port on a first node to a destination port on a second node, comprising: i) selecting, from a predetermined, exclusive list of authorized data pathways, a security port number exclusively paired with a port number of the destination port; ii) forming an encrypted communication pathway extending from the first node to a security port present on the second node, the security port having the selected security port number (i.e., the selected security port number assigned to the security port); iii) prior to transmitting any data from the source port to the destination port: verifying, at the first node, that a first n-tuple received from the encrypted communication pathway matches an expected value based on the security port number, the first n-tuple comprising: a nonpublic device code for the second node, a user associated with the destination port, an application associated with the destination port, and a data protocol descriptor; and iv) prior to passing a network packet to the destination port: verifying, at the second node, that an second n-tuple obtained from the network packet matches an expected value based on the security port number, the second n-tuple comprising: a user associated with the source port, an application associated with the source port, and the data protocol descriptor.

Certain embodiments may provide, for example, a method to instantiate and manage a dedicated data pathway extending from a source port on a first node to a destination port on a second node, comprising: selecting, from a predetermined, exclusive list of authorized data pathways, a tunnel port number exclusively paired with a port number of the destination port; forming a network tunnel extending from the first node to a tunnel port present on the second node, the tunnel port having the selected tunnel port number (i.e., the selected tunnel port number assigned to the tunnel port); iii) prior to transmitting any data from the source port to the destination port: verifying, at the first node, that a first n-tuple received from the network tunnel matches an expected value based on the tunnel port number, the first n-tuple comprising: a nonpublic device code for the second node, a user associated with the destination port, an application associated with the destination port, and a data protocol descriptor; and iv) prior to passing a network packet to the destination port: verifying, at the second node, that an second n-tuple obtained from the network packet matches an expected value based on the tunnel port number, the second n-tuple comprising: a user associated with the source port, an application associated with the source port, and the data protocol descriptor.

Certain embodiments may provide, for example, a system comprising: plural nodes communicating over a network according to a shared network protocol, wherein each one of the plural nodes may be preconfigured to initialize at least one encrypted network tunnel with at least another one of the plural nodes, and each one of the plural nodes having application and/or data transfer privileges may be limited to transferring data to another one of the plural nodes exclusively by an encrypted network tunnel of the at least one encrypted network tunnel.

A. In certain embodiments, for example, each one of the least 25% (for example at least 50%, such as at least 90%) of the plural nodes may be an edge computing device.

Certain embodiments may provide, for example, a method to retrofit a node interface to a network, comprising: inserting a computing device between a node and the network. In certain further embodiments, for example, the computing device may comprise: a file stored on non-transitory computer-readable storage medium, the file having a list of authorized data communications sessions, the file comprising: an index defined by an application authorized to be executed on a processor of the node and an authorized user of the application, a unique 2-tuple consisting of a port number assigned to the application and a port number assigned to a network security middleware, a unique 2-tuple consisting of a port number assigned to a remote application and a port number assigned to a remote network security middleware, and a data protocol descriptor.

Certain embodiments may provide, for example, a method to retrofit a node interface to a network, comprising: inserting a computing device between a node and the network, the computing device comprising: a file on a non-transitory computer-readable storage medium of the computing device, the file interpretable by network security middleware executing on the computing device to define authorized communication sessions and an authorized data protocol for each one of the authorized communication sessions. In certain further embodiments, for example, the computing device may further comprise a network stack configured to route each data packet through the network security middleware, the network security middleware configured to drop a data packet unless it is authorized to be transmitted using one of the authorized communication sessions.

Certain embodiments may provide, for example, a secure method for a first computing device to update resident software, comprising: receiving, from a predetermined, authenticated, authorized client executing on a second computing device, an encrypted non-executable payload noticing availability of updated software. In certain further embodiments, for example, the receiving may be followed by establishing a unidirectional encrypted network tunnel with a predetermined server executing on a third computing device. In certain further embodiments, for example, the establishing may comprise exchanging and authenticating encrypted device identifiers between the first computing device and the third computing device, and verifying that the second computing device and the third computing device are different devices. In certain further embodiments, for example, the method may further comprise downloading the updated software over the unidirectional encrypted network tunnel.

Certain embodiments may provide, for example, a secure computing device comprising a physical network interface, the physical network interface configured to: compare a destination port number of each incoming network packet to a list of authorized destination ports, execute remote procedure calls to first software program (or module or portion of code) executing on a central processing unit of the computing device, the first software configured to decrypt metadata from each incoming network packet, and execute remote procedure calls to second software executing on the central processing unit. In certain further embodiments, for example, the second software program may be configured to compare the decrypted metadata to a list of authorized n-tuples, each of the n-tuples in the list of authorized n-tuples comprising descriptors for: a source application for the incoming network packet, a user for the source application, and a payload protocol for the network packet.

A. In certain embodiments, for example, the physical network interface may be a field-programmable gate array.

B. In certain embodiments, for example, the physical network interface may be further configured (for example programmed) to execute remote procedure calls to a third software program executing on the central processing unit, the third software configured to translate a payload of the incoming network packet into native formatted data for consumption by the receiving application.

C. In certain embodiments, for example, at least one of the first software, second software, or third software execute in an OSI application layer of the computing device.

Certain embodiments may provide, for example, a method to filter a network packet in an edge computing device, comprising: parsing at least a portion of the network packet to obtain payload data in a network stack of the edge computing device; and invoking publish-subscribe pattern messaging software from a sub-session layer of the network stack to retrieve, based on at least a portion of the payload data, one or more network packet authentication and/or access control parameters.

A. In certain embodiments, for example, the publish-subscribe pattern messaging software may conform to the Data Distribution Service standard.

B. In certain embodiments, for example, the publish-subscribe pattern messaging software may conform to an MQ Telemetry Transport messaging protocol.

C. In certain embodiments, for example, the one or more network packet authentication and/or access control parameters may be retrieved from metadata encoded in the payload data. In certain embodiments, for example, the one or more network packet authentication and/or access control parameters may comprise a source application, a source application user, and a data protocol of the payload data. In certain embodiments, for example, the one or more network packet authentication and/or access control parameters may be encrypted. In certain embodiments, for example, the method may further comprise: comparing a port address number of the network packet to a list of pre-authorized port address numbers stored in kernel random access memory.

Certain embodiments may provide, for example, a method to filter a network packet (for example an IP packet containing an IP header and a TCP segment). In certain embodiments, for example, the method may comprise parsing the network packet to obtain network packet data; and invoking data distribution service software from a sub-session layer (for example a transport layer according to the Open Systems Interconnection model) of a network stack to retrieve, based on at least a portion of the network packet data (for example a metadata portion), one or more network packet authentication and/or access control parameters. In certain embodiments, for example, the network packet may be an incoming packet received from an Ethernet connection. In certain embodiments, for example, the network packet may be an outgoing packet being directed towards received from an Ethernet connection. In certain embodiments, for example, parsing the network packet may comprise parsing a header of the network packet (for example a network header such as an IP header, an IPsec header, or a TCP header of a TCP segment). In certain embodiments, for example, the one or more network packet authentication and/or access control parameters may comprise a destination port. In certain embodiments, for example, parsing the network packet may comprise parsing metadata (for example payload metadata). In certain further embodiments, for example, the metadata may comprise metadata useful for authenticating a computing device sending at least a portion of a payload present in the network packet. In certain embodiments, for example, the metadata may comprise metadata useful for authenticating an application and/or user sending at least a portion of a payload present in the network packet. In certain embodiments, for example, the metadata may comprise metadata useful for authorizing an application to have access to at least a portion of a payload present in the network packet.

A. In certain embodiments, for example, the network stack may be executing on a node in a data distribution service domain. In certain embodiments, for example, the node may be a subscriber in the data distribution service domain. In certain embodiments, for example, the node may be a publisher in the data distribution service domain. In certain embodiments, for example, the metadata may comprise metadata inserted by data distribution service middleware. In certain embodiments, for example, the metadata may comprise a publish-subscribe topic. In certain embodiments, for example, the network packet may comprise a payload having at least a portion that is strongly typed. In certain embodiments, for example, the metadata may comprise a publish-subscribe data type definition. In certain further embodiments, for example, the one or more network packet access control parameters may comprise the publish-subscribe data type definition. In certain embodiments, for example, the method may further comprise comparing the one or more network packet authentication and/or access control parameters with settings of a domain participant in a data distribution service domain. In certain embodiments, for example, the settings may define at least one data reader in the data distribution service domain. In certain embodiments, for example, the settings may define at least one data writer in the data distribution service domain. In certain embodiments, for example, the method may further comprise creating and maintaining an event log.

B. In certain further embodiments, for example, the data distribution service software may be invoked by operating system software, for example by operating system software operating at kernel priority. In certain embodiments, for example, the data distribution service software defines at least part of a software library, for example a pre-built library. In certain embodiments, for example, the data distribution service software defines at least one subroutine. In certain embodiments, for example, the data distribution service software defines at least one module. In certain embodiments, for example, the data distribution service software defines at least one function. In certain embodiments, for example, the data distribution service software defines at least a portion of an object.

C. In certain embodiments, for example, the network stack may be executing on a dedicated computing device. In certain embodiments, for example, the method may be performed at wire speed.

Certain embodiments may provide, for example, a kernel-based method for authorized network communication, comprising: detecting a network packet added to a network stack memory, moving the detected network packet from the network stack memory to a heap space; authorizing the network packet, and removing the authorized network packet from the heap space and replacing the network packet in network stack memory. In certain embodiments, for example, the authorizing may be based at least on: a) a universal identifier for a source of the network packet, comprising an authorized source application identifier and an identifier for an authorized user of the source application; b) a universal identifier for destination of the network packet, comprising an authorized destination application identifier and an identifier for an authorized user of the destination application; c) a port associated with the destination application; d) a different port associated with a middleware; and e) a data protocol field.

A. In certain embodiments, for example, the middleware may be responsible for the detecting. In certain embodiments, for example, the middleware may be responsible for the moving. In certain embodiments, for example, the middleware may be responsible for the authorizing. In certain embodiments, for example, the middleware may be responsible for the detecting, the moving, and the authorizing.

Certain embodiments may provide, for example, a kernel-based method for authorized network communication, comprising: i) detecting a network packet added to a network stack memory; ii) moving the detected network packet from the network stack memory to a heap space; iii) authorizing the network packet, based at least on: a) a universal identifier for a source of the network packet, comprising an authorized source application identifier and an identifier for an authorized user of the source application; b) a universal identifier for destination of the network packet, comprising an authorized destination application identifier and an identifier for an authorized user of the destination application; c) a port associated with the destination application; d) a different port associated with a middleware; and e) a data protocol field; and iv) removing the authorized network packet from the heap space and replacing the network packet in network stack memory.

Certain embodiments may comprise, for example, a kernel-based method for authorized network communication, comprising: detecting (for example receiving or intercepting) a network packet added to a network stack memory, making the detected network packet accessible to a heap space (for example by moving or copying the network packet from the network stack memory to the heap space), authorizing the network packet, and removing the authorized network packet from the heap space and replacing the network packet in network stack memory. In certain further embodiments, for example, the authorizing may reference: an index defined by a pre-approved application a pre-approved user of the application, a unique 2-tuple consisting of a port number assigned to the application and a port number assigned to an encryption layer, a unique 2-tuple consisting of a port number assigned to a remote application and a port number assigned to a remote encryption layer, and a data protocol field.

Certain embodiments may provide, for example, a method to prevent an attack by malware resident on a node, comprising: a network security agent opening a port in listening mode, the port configured to establish a compromised encrypted connection, receiving a connection request at the port from a malware configured to exploit the compromised encryption protocol, establishing an encrypted tunnel between the network security agent and the malware, the encrypted tunnel having the port as an endpoint, and the network security agent terminating the encrypted tunnel after a fixed number of attempts by the malware to provide an expected identification code for the node, the expected identification code selected by the network security agent based on the port number of the port.

A. In certain embodiments, for example, the network security agent may be present on the node, processor, or computing device. In certain embodiments, for example, the network security agent may be present on a remote node, processor, or computing device. In certain embodiments, for example, the encrypted connection may be compromised due to a compromised private key. In certain embodiments, for example, the encrypted connection may be compromised due to one or more compromised components of a cipher suite. In certain embodiments, for example, the encrypted connection may be compromised due to one or more security holes in a software implementation of an encryption protocol. In certain embodiments, for example, the malware may be present on the node, processor, or computing device. In certain embodiments, for example, the malware may be present on a different node, processor, or computing device. In certain embodiments, for example, the port may be configured according to a secure socket layer protocol. In certain embodiments, for example, the port may be configured according to an IPsec protocol. In certain embodiments, for example, the malware may identify the port based on a port scan. In certain embodiments, for example, the expected node identification code may have a length of at least 2048 bits. In certain embodiments, for example, the sum-of-digits of the expected node identification code may be a prime number. In certain embodiments, for example, a portion of the expected node identification code may be a randomly generated number. In certain embodiments, for example, at least 90% of the digits of the expected node identification code may be a randomly generated number. In certain embodiments, for example, the expected node identification code may be stored in a proprietary binary format configured to be interpreted solely by the network security agent. In certain embodiments, for example, the expected node identification code may be stored on a non-transitory computer-readable storage medium (for example a nonvolatile memory storage medium) in an encrypted, read-only binary file, the binary file comprising a proprietary record structure. In certain embodiments, for example, the binary file may comprise plural records having variable record length. In certain embodiments, for example, the binary file may be readable into random access memory solely by the network security agent. In certain embodiments, for example, the security agent may terminate the encrypted tunnel after no more than 20 attempts to provide the expected identification code.

Certain embodiments may provide, for example, a method to prevent an attack by malware resident on a node, comprising: a network security agent sending a connection request to a spoofed listening port associated with a malware, the network security agent configured to establish a compromised encrypted connection, establishing an encrypted tunnel between the network security agent and the malware, the encrypted tunnel having the malware port as an endpoint, and the network security agent terminating the encrypted tunnel after a fixed number of attempts by the malware to provide an expected identification code for the node, the expected identification code selected by the network security agent based on the port number of the port. In certain embodiments, for example, the network security agent may inadvertently send the connection request to the spoofed listening port. In certain embodiments, for example, the network security agent may be directed (for example by malware) to send the connection request to the spoofed listening port.

Certain embodiments may provide, for example, a method to prevent an attack by malware resident on a node, comprising: the malware attempting to transmit a connection request to a remote destination port, and checking an application code (for example an application code obtained from process status check) and a user code value of the malware against expected values, the expected values selected based on the destination port.

A. In certain embodiments, for example, the method may further comprise dropping the connection request based on the application code and a user code failing to match the expected values. In certain embodiments, for example, the method may further comprise dropping the connection request based on the absence of the destination port in a preconfigured list of allowed destination ports. In certain embodiments, for example, the malware may be introduced to the node via a USB port.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, processor, or computing device. In certain embodiments, for example, the method may comprise establishing an encrypted connection to transfer data exclusively between a first process running on the first node and a second process running on the second node, processor, or computing device. In certain embodiments, for example, the establishing may comprise the second node receiving a node identification packet from the first node and confirming a shared secret node identification code received from the first node, processor, or computing device. In certain embodiments, for example, the method may comprise managing a connection state of the authorized encrypted connection. In certain embodiments, for example, the managing may comprise confirming that network packets received at the second node via the encrypted connection comprise at least a predetermined user identification code, a predetermined process identification code, and/or a predetermined data protocol identification code. In certain embodiments, for example, the node identification packet may comprise a packet type header configured for processing by network security software. In certain embodiments, for example, the network security software may be invoked in a network stack. In certain further embodiments, for example, the packet type header may be located after a layer three header according to the OSI Seven Layer Model. In certain further embodiments, for example, the packet type header may be located after a layer four header according to the OSI Seven Layer Model. In certain further embodiments, for example, the packet type header may be located after an SSL/TLS header. In certain embodiments, for example, a data protocol of the data to be transferred may match an expected data protocol based on the data protocol identification code. In certain embodiments, for example, the predetermined user identification code, the predetermined process identification code, and/or the predetermined data protocol identification code may be metadata present in the network packets. In certain embodiments, for example, the metadata may be configured for processing by network security software. In certain embodiments, for example, the network security software may be invoked in a network stack. In certain further embodiments, for example, the packet type header may be located after a layer three header according to the OSI Seven Layer Model. In certain further embodiments, for example, the metadata may be located after a layer four header according to the OSI Seven Layer Model. In certain further embodiments, for example, the packet type header may be located after an SSL/TLS header.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, processor, or computing device. In certain embodiments, for example, the method may comprise authorizing an encrypted connection to transfer data exclusively between a first process (for example a first user process) running on the first node and a second process (for example a second user process) running on the second node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise transmitting a node identification packet from the first node to the second node, the node identification packet comprising a shared secret node identification code for the first node, processor, or computing device. In certain embodiments, for example, the authorizing may be followed by managing a connection state of the authorized encrypted connection. In certain embodiments, for example, the managing may comprise withdrawing the authorization if at least one network packet received from the authorized encrypted connection is missing one or more of an expected user identification code, process identification code, and data protocol identification code. In certain embodiments, for example, the authorizing may further comprise: transmitting a node identification packet from the second node to the first node, the node identification packet comprising a shared secret node identification code for the second node, processor, or computing device. In certain embodiments, for example, the authorizing may further comprise: transmitting a process identification packet from the first node to the second node, the process identification packet comprising a user identifier for the first process, an application identifier for the first process, a data protocol identifier for the connection, or a combination of two or more of the foregoing identifiers. In certain embodiments, for example, the authorizing may further comprise: executing operating system commands to identify a process requesting the data transfer, followed by verifying that the requesting process is authorized to transfer and/or receive the data. In certain embodiments, for example, the managing may further comprise: executing operating system commands to identify a process requesting the data transfer, followed by verifying that the requesting process is authorized to transfer and/or receive the data. In certain embodiments, for example, the authorizing may comprise consulting configuration files present on the first node and second node to obtain one or more of the shared secret node identification code, user identification code, process identification code, and data protocol identification code. In certain embodiments, for example, the managing may comprise consulting configuration files present on the first node and second node to obtain one or more of the shared secret node identification code, user identification code, process identification code, and data protocol identification code. In certain embodiments, for example, a 3-tuple comprising the user identification code, process identification code, and data protocol identification code may be a shared secret between the first node and the second node, processor, or computing device. In certain embodiments, for example, a 4-tuple comprising the shared secret node identification code, user identification code, process identification code, and data protocol identification code may be a shared secret between the first node and the second node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise mutual exchange from and authorization by the first node and second node of one or more of the shared secret node identification code, user identification code, process identification code, and data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, processor, or computing device. In certain embodiments, for example, the method may comprise authorizing an encrypted connection to transfer data between a first process running on the first node and a second process running on the second node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise mutual exchange, authentication, and authorization of shared secret first and second node identification codes. In certain embodiments, for example, the authorizing may be followed by managing a connection state of the authorized encrypted connection. In certain embodiments, for example, the managing may comprise dropping the connection if an incoming network packet from the authorized encrypted connection is missing one or more of an expected user identification code, process identification code, and data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, processor, or computing device. In certain embodiments, for example, the method may comprise authorizing an encrypted connection to transfer data exclusively between a first process running on the first node and a second process running on the second node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise transmitting a node identification packet from the first node to the second node, the node identification packet comprising a shared secret node identification code for the first node, processor, or computing device. In certain embodiments, for example, the authorizing may be followed by managing a connection state of the authorized encrypted connection. In certain embodiments, for example, the managing may comprise withdrawing the authorization if at least one network packet received from the authorized encrypted connection is missing an expected user, process, and/or packet payload data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, comprising: i) establishing an encrypted connection to transfer data exclusively between a first process running on the first node and a second process running on the second node, comprising: the second node receiving a node identification packet from the first node and confirming a shared secret node identification code received from the first node; and ii) managing a connection state of the authorized encrypted connection, comprising: confirming that network packets received at the second node via the encrypted connection comprise at least an predetermined user identification code, a predetermined process identification code, and/or a predetermined data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, comprising: i) authorizing an encrypted connection to transfer data exclusively between a first process running on the first node and a second process running on the second node, comprising: transmitting a node identification packet from the first node to the second node, the node identification packet comprising a shared secret node identification code for the first node; followed by ii) managing a connection state of the authorized encrypted connection, comprising: withdrawing the authorization if at least one network packet received from the authorized encrypted connection is missing one or more of an expected user identification code, process identification code, and data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, comprising: i) authorizing an encrypted connection to transfer data between a first process running on the first node and a second process running on the second node, comprising: mutual exchange, authentication, and authorization of shared secret first and second node identification codes; followed by ii) managing a connection state of the authorized encrypted connection, comprising: dropping the connection if an incoming network packet from the authorized encrypted connection is missing one or more of an expected user identification code, process identification code, and data protocol identification code.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, comprising: i) authorizing an encrypted connection to transfer data exclusively between a first process running on the first node and a second process running on the second node, comprising: transmitting a node identification packet from the first node to the second node, the node identification packet comprising a shared secret node identification code for the first node; followed by ii) managing a connection state of the authorized encrypted connection, comprising: withdrawing the authorization if at least one network packet received from the authorized encrypted connection is missing an expected user, process, and/or packet payload data protocol identification code.

Certain embodiments may provide, for example, a method of securing network communications received by a network node, processor, or computing device. In certain embodiments, for example, the method may comprise confirming network packets received are from a preconfigured, predefined, pre-established and/or preprovisioned source process running on a preconfigured, predefined, pre-established and/or preprovisioned authorized source node and directed to a preconfigured, predefined, pre-established and/or preprovisioned authorized destination process running on a preconfigured, predefined, pre-established and/or preprovisioned authorized destination node, processor, or computing device. In certain embodiments, for example, the method may further comprise passing at least a portion of the payloads from the network packets to the authorized destination process.

A. In certain embodiments, for example, the authorized source process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the network node (for example the network node may contain a file identifying the source process, wherein the file is present on the network node prior to the confirming and passing). In certain embodiments, for example, the authorized source node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the network node (for example the network node may contain a file identifying the source node, wherein the file is present on the network node prior to the confirming and passing). In certain embodiments, for example, the authorized destination process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the network node (for example the network node may contain a file identifying the destination process, wherein the file is present on the network node prior to the confirming and passing). In certain embodiments, for example, the authorized destination node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the network node (for example the network node may contain a file identifying the destination node, wherein the file is present on the network node prior to the confirming and passing). In certain embodiments, for example, the authorized source process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized source node (for example the authorized source node may contain a file identifying the source process, wherein the file is present on the authorized source node prior to the confirming and passing). In certain embodiments, for example, the authorized source node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized source node (for example the authorized source node may contain a file identifying the source node, wherein the file is present on the authorized source node prior to the confirming and passing). In certain embodiments, for example, the authorized destination process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized source node (for example the authorized source node may contain a file identifying the destination process, wherein the file is present on the authorized source node prior to the confirming and passing). In certain embodiments, for example, the authorized destination node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized source node (for example the authorized source node may contain a file identifying the destination node, wherein the file is present on the authorized source node prior to the confirming and passing). In certain embodiments, for example, the authorized source process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized destination node (for example the authorized destination node may contain a file identifying the source process, wherein the file is present on the authorized destination node prior to the confirming and passing). In certain embodiments, for example, the authorized source node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized destination node (for example the authorized destination node may contain a file identifying the source node, wherein the file is present on the authorized destination node prior to the confirming and passing). In certain embodiments, for example, the authorized destination process may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized destination node (for example the authorized destination node may contain a file identifying the destination process, wherein the file is present on the authorized destination node prior to the confirming and passing). In certain embodiments, for example, the authorized destination node may be preconfigured, predefined, pre-established and/or preprovisioned relative to the authorized destination node (for example the authorized destination node may contain a file identifying the destination node, wherein the file is present on the authorized destination node prior to the confirming and passing).

B. In certain embodiments, for example, the received packets may be received via an authorized encrypted communication pathway, wherein the authorized encrypted communication pathway may be established, wherein the establishing of the authorized encrypted communication pathway may comprise authorizing a preconfigured, predefined, pre-established and/or preprovisioned source node and a preconfigured, predefined, pre-established and/or preprovisioned destination node, processor, or computing device.

C. In certain embodiments, for example, the authorized destination node may be the network node, processor, or computing device. In certain embodiments, for example, the authorized destination node may perform the confirming and passing.

D. In certain embodiments, for example, the confirming may be transparent to the authorized source process. In certain embodiments, for example, the confirming may be transparent to the authorized destination process. In certain embodiments, for example, the confirming may be transparent to the authorized source process and the authorized destination process. In certain embodiments, for example, the confirming may comprise: comparing destination port numbers of the network packets with a preconfigured, predefined, pre-established and/or preprovisioned port number associated with the authorized destination process. In certain embodiments, for example, the associated port may be assigned to the authorized destination process. In certain embodiments, for example, the associated port may be assigned to network security software in communication with the authorized destination process. In certain embodiments, for example, the confirming may comprise: obtaining destination port numbers and source application codes, source process owners, and/or data type protocol from the network packets; selecting one or plural preconfigured, predefined, pre-established and/or preprovisioned authorization codes assigned to the destination port numbers; and matching the source application codes, source process owners, and/or data type protocol obtained from the network packets to the one or plural authorization codes.

E. In certain embodiments, for example, the passing may comprise transmitting the least a portion of the payloads from the network packets on a dedicated communication pathway for the authorized source process. In certain embodiments, for example, the passing may comprise transmitting the at least a portion of the payloads from the network packets via a loopback interface. In certain embodiments, for example, the passing may comprise passing the at least a portion of the payloads from the network packets via kernel functions (for example read and/or write functions). In certain embodiments, for example, the passing may comprise copying the at least a portion of the payloads from one memory location to another memory location. In certain embodiments, for example, the passing may not comprise copying the at least a portion of the payloads from one memory location to another memory location. In certain embodiments, for example, the passing may comprise adjusting a pointer to a location in kernel memory.

F. In certain embodiments, for example, the method may further comprise: establishing an authorized connection having the associated port as an endpoint, followed by receiving the network packets received.

Certain embodiments may provide, for example, a method of securing network communications received by a network node, processor, or computing device. In certain embodiments, for example, the method may comprise establishing an authorized encrypted communication pathway, which may comprise authorizing a preconfigured, predefined, pre-established and/or preprovisioned source node and a preconfigured, predefined, pre-established and/or preprovisioned destination node, processor, or computing device. In certain embodiments, for example, the method may comprise confirming network packets received via the encrypted communication pathway are from a preconfigured, predefined, pre-established and/or preprovisioned authorized source process running on the authorized source node and directed to a preconfigured, predefined, pre-established and/or preprovisioned authorized destination process running on the authorized destination node, processor, or computing device. In certain embodiments, for example, the method may comprise passing at least a portion of the payloads from the network packets to the authorized destination process. In certain embodiments, for example, the source node and the destination node may authorize one another based on mutual exchange, authentication, and authorization of shared secret device codes between the source node and the destination node, processor, or computing device. In certain embodiments, for example, the mutual exchange may be made across the encrypted communication pathway prior to its authorization. In certain embodiments, for example, the shared secret device codes may be created independently of any internet protocol. In certain embodiments, for example, the encrypted communication pathway may be formed according to SSL/TLS protocol prior to its authorization. In certain embodiments, for example, the encrypted communication pathway may be formed according to IPsec protocol prior to its authorization. In certain embodiments, for example, the encrypted communication pathway may be formed according to L2TP protocol prior to its authorization.

Certain embodiments may provide, for example, a method of securing network communications received by a network node, comprising: i) confirming network packets received are from a preconfigured, predefined, pre-established and/or preprovisioned authorized source process running on a preconfigured, predefined, pre-established and/or preprovisioned authorized source node and directed to a preconfigured, predefined, pre-established and/or preprovisioned authorized destination process running on a preconfigured, predefined, pre-established and/or preprovisioned authorized destination node; and ii) passing at least a portion of the payloads from the network packets to the authorized destination process.

Certain embodiments may provide, for example, a method of securing network communications received by a network node, comprising: i) establishing an authorized encrypted communication pathway, comprising authorizing a preconfigured, predefined, pre-established and/or preprovisioned source node and a preconfigured, predefined, pre-established and/or preprovisioned destination node; ii) confirming network packets received via the encrypted communication pathway are from a preconfigured, predefined, pre-established and/or preprovisioned authorized source process running on the authorized source node and directed to a preconfigured, predefined, pre-established and/or preprovisioned authorized destination process running on the authorized destination node; and iii) passing at least a portion of the payloads from the network packets to the authorized destination process.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, processor, or computing device. In certain embodiments, for example, the method may comprise pre-loading a first configuration file (for example a preprovisioned first configuration file) on the first node (for example loading the file onto a non-transitory computer-readable storage medium (for example a nonvolatile memory storage medium) of the first node prior to boot-up of the first node, or loading the file into memory of the first node prior to other steps of the method enumerated herein) and a second configuration file (for example a preprovisioned second configuration file) on the second node, processor, or computing device. In certain embodiments, for example, the method may comprise forming an encrypted communication pathway. In certain embodiments, for example, the method may comprise authorizing the encrypted communication pathway to transfer data between a first process running on the first node and a second process running on the second node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise transmitting a first node identification packet from the first node to the second node, the first node identification packet comprising a payload having a first node identifier assigned to the first node, the first node identifier obtained from the pre-loaded first configuration file on the first node, processor, or computing device. In certain embodiments, for example, the authorizing may comprise comparing the first node identifier from the first node identification packet with a further node identifier assigned to the first node, the further node identifier obtained from the pre-loaded second configuration file on the second node, processor, or computing device. In certain embodiments, for example, the data may comprise an executable program, a program command, typed data, a combination of two or more of the foregoing, or a portion of one of the foregoing.

A. In certain embodiments, for example, the method may be transparent to the first process and the second process (for example the first process and the second process may execute first and second compiled code whether or not the method is invoked, or each of the source code for the first process and the source code for the second process may interface with a network stack using standard function syntax of a network application programmer's interface).

B. In certain embodiments, for example, the first node identification packet may be transmitted through the encrypted communication pathway. In certain embodiments, for example, the first node identifier may be nonpublic and a shared secret. In certain embodiments, for example, the first node identifier may be nonpublic. In certain embodiments, for example, the first node identifier may be a shared secret between the first node and the second node, processor, or computing device. In certain embodiments, for example, the first node identifier may not be an IP address. In certain embodiments, for example, the first node identifier may not be a MAC address. In certain embodiments, for example, the first node identifier may not be a parameter used in (or a field present in) a layer 2-5 protocol header according to the OSI model.

C. In certain embodiments, for example, the comparing may be performed by network security software, the network security software invoked in a network stack of the second node, processor, or computing device. In certain embodiments, for example, the network security software may be transparent to the first process and the second process. In certain embodiments, for example, an interface to the network security software may be invoked using standard network API syntax.

D. In certain embodiments, for example, the first configuration file may be pre-loaded on first nonvolatile storage media (for example first physical nonvolatile storage media) and the second configuration file may be pre-loaded on second nonvolatile storage media (for example second physical nonvolatile storage media). In certain embodiments, for example, the pre-loaded second configuration file may comprise at least one record, no more than one of the at least one record comprising an n-tuple consisting of the first node identifier and one or more of a first application code, first process owner code, and first data type code. In certain embodiments, for example, the at least one record may comprise an identifier, the identifier used in forming the encrypted communication pathway. In certain embodiments, for example, the identifier may be a cryptographic primitive (for example a prime number, or for example a private key). In certain embodiments, for example, the at least one record may be a variable length record. In certain embodiments, for example, the second configuration file may be an encrypted binary file.

E. In certain embodiments, for example, the method may further comprise: transmitting a data packet from the first node to the second node, the data packet comprising a payload, the payload comprising: data from the first process; and at least one first process identifier comprising one or more of an application code (i.e., a code or identifier assigned to the application), process owner code, and data type code, the at least one first process identifier assigned to the first node, the at least one first process identifier obtained from the pre-loaded first configuration file on the first node, processor, or computing device. In certain embodiments, for example, the data may conform (for example the formatting of the data may conform) to a data type assigned to the data type code.

F. In certain embodiments, for example, the method may further comprise: comparing the at least one first process identifier with an at least one process identifier assigned to the first process, the at least one process identifier obtained from the pre-loaded second configuration file on the second node, processor, or computing device. In certain embodiments, for example, the method may further comprise: updating an authorized connection list to show an open connection state for the authorized encrypted communication pathway.

G. In certain embodiments, for example, the method may further comprise: transmitting data packets from the first node to the second node, the data packets comprising payloads, each of the payloads comprising: data from the first process; and at least one first process identifier comprising one or more of an application code, process owner code, and data type code, the at least one first process identifier assigned to the first node, the at least one first process identifier obtained from the pre-loaded first configuration file on the first node, processor, or computing device. In certain embodiments, for example, the method may further comprise: checking an authorized connection list resident on the second node to confirm that the encrypted communication pathway is in an open connection state. In certain embodiments, for example, the at least one first process identifier may be positioned in the payload to be processed by network security software. In certain embodiments, for example, the processing may be timed to occur prior to the processing of any application layer protocol header. In certain embodiments, for example, the method may further comprise: comparing the at least one first process identifier contained in each one of the payloads with an at least one process identifier assigned to the first process, the at least one process identifier obtained from the pre-loaded second configuration file on the second node, processor, or computing device. In certain embodiments, for example, the method may further comprise: updating an authorized connection list to change the authorized encrypted communication pathway connection state from open to closed if the at least one first process identifier contained in at least one of the payloads does not match the at least one first process identifier obtained from the pre-loaded first configuration file on the first node, processor, or computing device.

H. In certain embodiments, for example, the authorizing may comprise: transmitting a second node identification packet from the second node to the first node, the second node identification packet comprising a payload having a second node identifier assigned to the second node, the second node identifier obtained from the pre-loaded second configuration file on the second node; and comparing the second node identifier from the second node identification packet with an additional node identifier assigned to the second node, the additional node identifier obtained from the pre-loaded first configuration file on the first node, processor, or computing device.

I. In certain embodiments, for example, the authorizing may comprise: transmitting a first process identification packet from the first node to the second node, the first process identification packet comprising a payload having at least one first process identifier assigned to the first process, the at least one first process identifier comprising one or more of a first application code, first process owner code, and first data type code, the at least one first process identifier assigned to the first node, the first process identifier obtained from the pre-loaded first configuration file on the first node; and comparing the at least one first process identifier from the first process identification packet with a further at least one process identifier assigned to the first node, the further at least one process identifier obtained from the pre-loaded second configuration file on the second node, processor, or computing device.

J. In certain embodiments, for example, the authorizing may comprise: transmitting a second process identification packet from the second node to the first node, the second process identification packet comprising a payload having at least one second process identifier assigned to the second process, the at least one second process identifier comprising one or more of a second application code, second process owner code, and second data type code, the at least one second process identifier assigned to the second node, the second process identifier obtained from the pre-loaded second configuration file on the first node; and comparing the at least one second process identifier from the second process identification packet with an additional at least one process identifier assigned to the second node, the additional at least one process identifier obtained from the pre-loaded first configuration file on the second node, processor, or computing device.

K. In certain embodiments, for example, the method may further comprise: executing operating system commands to identify a process requesting the data transfer, followed by verifying that the requesting process is the first process.

Certain embodiments may provide, for example, a method for communication between a first node and a second node, comprising: i) pre-loading a first configuration file on the first node and a second configuration file on the second node; ii) forming an encrypted communication pathway; and iii) authorizing the encrypted communication pathway to transfer data between a first process running on the first node and a second process running on the second node, comprising: a) transmitting a first node identification packet from the first node to the second node, the first node identification packet comprising a payload having a first node identifier assigned to the first node, the first node identifier obtained from the pre-loaded first configuration file on the first node; and b) comparing the first node identifier from the first node identification packet with a further node identifier assigned to the first node, the further node identifier obtained from the pre-loaded second configuration file on the second node, processor, or computing device.

Certain embodiments may provide, for example, a method for authorized network communication. In certain embodiments, for example, the method may comprise: establishing a communication pathway between a first processor node and a second processor node, processor, or computing device. In certain embodiments, for example, the method may comprise comparing a second node identification code obtained from a second node identification packet against a second node expected value. In certain embodiments, for example, the method may comprise further comparing a first node identification code obtained from a first node identification packet against a first node expected value. In certain embodiments, for example, the method may comprise transmitting, after the comparing and further comparing, application data via the communication pathway.

A. In certain embodiments, for example, the first processor node may execute the comparing. In certain embodiments, for example, the second processor node may execute the further comparing. In certain embodiments, for example, the comparing and further comparing may follow the establishing. In certain embodiments, for example, the transmitting may be executed only after the comparing and further comparing.

B. In certain embodiments, for example, the communication pathway may be encrypted. In certain embodiments, for example, the first node identification code may be encrypted in the first node identification packet with a first single-use encryption key; and/or the second node identification code is encrypted in the second node identification packet with a second single-use encryption key.

C. In certain embodiments, for example, the first node identification code and/or the second node identification code may be nonpublic. In certain embodiments, for example, the first node identification code and/or the second node identification code may be a shared secret. In certain embodiments, for example, the second node expected value may be pre-provisioned on the first processor node; and/or the first node expected value may be pre-provisioned on the second processor node, processor, or computing device.

D. In certain embodiments, for example, the first node identification packet may comprise a higher-than-OSI layer three header, the a higher-than-OSI layer three header comprising a packet type indicator, the packet type indicator interpretable by network security software to alert the network security software to expect the first node identification code. In certain embodiments, for example, the second node identification packet may comprise a higher-than-OSI layer three header, the a higher-than-OSI layer three header comprising a packet type indicator, the packet type indicator interpretable by network security software to alert the network security software to expect the second node identification code.

E. In certain embodiments, for example, the first node identification packet and the second node identification packet may be received via the communication pathway. In certain embodiments, for example, the first node identification packet and the second node identification packet may be received via the network. In certain embodiments, for example, the first node identification packet and the second node identification packet may not be received via the communication pathway.

Certain embodiments may provide, for example, a method for authorized network communication. In certain embodiments, for example, the method may comprise: i) establishing a communication pathway between a first processor node and a second processor node; ii) comparing a second node identification code obtained from a second node identification packet against a second node expected value; iii) further comparing a first node identification code obtained from a first node identification packet against a first node expected value; and iv) transmitting, after the comparing and further comparing, application data via the communication pathway.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device, comprising: comparing a destination computing device nonpublic identification code obtained from the destination computing device with a destination computing device pre-established value. In certain embodiments, for example, the destination computing device pre-established value may be preprovisioned on the source computing device.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: comparing a destination computing device nonpublic identification code obtained from the destination computing device with a destination computing device pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device. In certain embodiments, for example, the forming a communication pathway may comprise comparing a destination computing device nonpublic identification code obtained from the destination computing device via the network with a destination computing device pre-established value. In certain embodiments, for example, the forming a communication pathway may comprise further comparing a source computing device nonpublic identification code obtained from the source computing device via the network to a source computing device pre-established value.

A. In certain embodiments, for example, the comparing and the further comparing may be performed independently. In certain embodiments, for example, the comparing and the further comparing may be performed sequentially. In certain embodiments, for example, the further comparing may not be performed until after the comparing is performed. In certain embodiments, for example, the comparing may not be performed until after the further comparing is performed. In certain embodiments, for example, the comparing and the further comparing may be performed asynchronously. In certain embodiments, for example, the comparing and the further comparing may be performed in a predetermined sequence.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: a) comparing a destination computing device nonpublic identification code obtained from the destination computing device via the network with a destination computing device pre-established value; and b) comparing a source computing device nonpublic identification code obtained from the source computing device via the network to a source computing device pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device. In certain embodiments, for example, the forming a communication pathway may comprise comparing a destination computing device nonpublic identification code obtained from the destination computing device via the network with a destination computing device pre-established value. In certain embodiments, for example, the forming a communication pathway may comprise further comparing a source computing device nonpublic identification code obtained from the source computing device via the network to a source computing device pre-established value. In certain embodiments, for example, the forming a communication pathway may comprise additionally comparing user-application identifiers and a payload data-type identifiers exchanged between the source and destination computing devices with predefined authorization codes.

A. In certain embodiments, for example, the comparing, further comparing, and additionally comparing may be performed independently. In certain embodiments, for example, the comparing, further comparing, and additionally comparing may be performed sequentially. In certain embodiments, for example, the further comparing may not be performed until after the comparing is performed. In certain embodiments, for example, the comparing may not be performed until after the further comparing is performed, and the additionally comparing may not be performed until after the further comparing is performed. In certain embodiments, for example, the comparing, further comparing, and additionally comparing may be performed asynchronously. In certain embodiments, for example, the comparing, further comparing, and additionally comparing may be performed in a predetermined sequence.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: a) comparing a destination computing device nonpublic identification code obtained from the destination computing device via the network with a destination computing device pre-established value; b) comparing a source computing device nonpublic identification code obtained from the source computing device via the network to a source computing device pre-established value; and c) comparing user-application identifiers and a payload data-type identifiers exchanged between the source and destination computing devices with predefined authorization codes.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device. In certain embodiments, for example, the forming a communication pathway may comprise comparing, on the source computing device, a destination computing device nonpublic identification code obtained via the network with a destination computing device pre-established value.

A. In certain embodiments, for example, the destination computing device nonpublic identification code may be provided by the destination computing device. In certain embodiments, for example, the destination computing device nonpublic identification code may not be provided by the destination computing device. In certain embodiments, for example, the destination computing device nonpublic identification code may be provided by a node, the node different from the destination computing device.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: comparing, on the source computing device, a destination computing device nonpublic identification code obtained via the network with a destination computing device pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device. In certain embodiments, for example, the forming a communication pathway may comprise comparing, on the source computing device, a destination computing device nonpublic identification code obtained from the destination computing device with a destination computing device pre-established value. In certain embodiments, for example, the forming a communication pathway may comprise comparing, on the destination computing device, a source computing device nonpublic identification code obtained from the source computing device to a source computing device pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: a) comparing, on the source computing device, a destination computing device nonpublic identification code obtained from the destination computing device with a destination computing device pre-established value; and b) comparing, on the destination computing device, a source computing device nonpublic identification code obtained from the source computing device to a source computing device pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: forming a communication pathway between a source computing device and a destination computing device. In certain embodiments, for example, the forming a communication pathway may comprise comparing, at the source computing device, a destination computing device nonpublic identification code obtained from a destination node packet with a destination node pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: forming a communication pathway between a source computing device and a destination computing device, comprising: comparing, at the source computing device, a destination computing device nonpublic identification code obtained from a destination node packet with a destination node pre-established value.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise: establishing authorized communication pathways for port-to-port network communications among the plurality of computing devices. In certain embodiments, for example, the establishing authorized communication pathways may comprise intercepting a network connection request from a source port, the request having an associated destination port number. In certain embodiments, for example, the establishing authorized communication pathways may comprise verifying that the source port is authorized to communicate with a destination port having the associated destination port number. In certain embodiments, for example, the establishing authorized communication pathways may comprise authorizing a communication pathway between a source computing device hosting the source port and a destination computing device hosting the destination port prior to any transmission of application data between the source computing device and the destination computing device via the communication pathway. In certain embodiments, for example, the authorizing may comprise comparing, on the source computing device, a destination computing device nonpublic identification code to a destination computing device expected value, the destination computing device nonpublic identification code obtained from a destination computing device identification packet. In certain embodiments, for example, the authorizing may comprise further comparing, on the destination computing device, a source computing device nonpublic identification code to a source computing device expected value, the source computing device nonpublic identification code obtained from a source computing device identification packet.

A. In certain embodiments, for example, the destination computing device identification packet and/or the source computing device identification packet may be received via the network. In certain embodiments, for example, the destination computing device identification packet and/or the source computing device identification packet may be received via the communication pathway.

B. In certain embodiments, for example, the destination computing device expected value may be pre-provisioned on the source computing device. In certain embodiments, for example, the source computing device expected value may be pre-provisioned on the destination computing device.

C. In certain embodiments, for example, the comparing and/or the further comparing may be enabled by a kernel of the computing device. In certain embodiments, for example, the computer-readable program code may be executable (or compilable, linkable, and/or loadable to be executable) by a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system).

D. In certain embodiments, for example, the communication management operations may comprise: inserting the source computing device nonpublic identification code into a higher-than-OSI layer three portion of the source computing device identification packet. In certain embodiments, for example, the communication management operations may comprise: inserting the source computing device nonpublic identification code into a higher-than-OSI layer four portion of the source computing device identification packet. In certain embodiments, for example, the communication management operations may comprise: inserting the source computing device nonpublic identification code into a payload portion of the source computing device identification packet. In certain embodiments, for example, the communication management operations may comprise: inserting the destination computing device nonpublic identification code into a higher-than-OSI layer three portion of the destination computing device identification packet. In certain embodiments, for example, the communication management operations may comprise: inserting the destination computing device nonpublic identification code into a higher-than-OSI layer four portion of the destination computing device identification packet. In certain embodiments, for example, the communication management operations may comprise: inserting the destination computing device nonpublic identification code into a payload portion of the destination computing device identification packet.

E. In certain embodiments, for example, the communication management operations may comprise: encrypting the source computing device nonpublic identification code and inserting the encrypted source computing device nonpublic identification code into the source computing device identification packet. In certain embodiments, for example, the source computing device nonpublic identification code may be encrypted with a single-use cryptographic key. In certain embodiments, for example, the communication management operations may comprise: encrypting the destination computing device nonpublic identification code and inserting the encrypted destination computing device nonpublic identification code into the destination computing device identification packet. In certain embodiments, for example, the destination computing device nonpublic identification code is encrypted with a single-use cryptographic key.

F. In certain embodiments, for example, the communication pathway between the source computing device and the destination computing device may be established prior to the authorizing.

G. In certain embodiments, for example, the communication management operations may comprise: requesting negotiation of the communication pathway, the requesting comprising sending a connection request packet comprising the associated destination port number.

H. In certain embodiments, for example, the communication management operations may comprise: establishing authorized encrypted communication pathways for all port-to-port network communications among the plurality of networked processor nodes.

I. In certain embodiments, for example, the communication management operations may comprise: comparing user-application identifiers and a payload data-type identifiers exchanged between the source and destination computing devices with predefined authorization codes.

J. In certain embodiments, for example, the comparing and the further comparing may be performed independently. In certain embodiments, for example, the comparing and the further comparing may be performed sequentially. In certain embodiments, for example, the further comparing may not be performed until after the comparing is performed. In certain embodiments, for example, the comparing may not be performed until after the further comparing is performed. In certain embodiments, for example, the comparing and the further comparing may be performed asynchronously. In certain embodiments, for example, the comparing and the further comparing may be performed in a predetermined sequence.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: establishing authorized communication pathways for port-to-port network communications among the plurality of computing devices, comprising: i) intercepting, via a network, a network connection request from a source port, the request having an associated destination port number; ii) verifying that the source port is authorized to communicate with a destination port having the associated destination port number; and iii) authorizing a communication pathway between a source computing device hosting the source port and a destination computing device hosting the destination port prior to any transmission of application data between the source computing device and the destination computing device via the communication pathway, comprising: a) comparing, on the source computing device, a destination computing device nonpublic identification code to a destination computing device expected value, the destination computing device nonpublic identification code obtained from a destination computing device identification packet; and b) further comparing, on the destination computing device, a source computing device nonpublic identification code to a source computing device expected value, the source computing device nonpublic identification code obtained from a source computing device identification packet.

Certain embodiments may provide, for example, a method for secure communication between applications on two nodes. In certain embodiments, for example, the method may comprise intercepting, at a first node, a network connection request from a resident first user-application to send data to a destination port on a second node, processor, or computing device. In certain embodiments, for example, the method may comprise consulting a first local policy on the first node to verify that the first user-application is authorized to send data to the destination port. In certain embodiments, for example, the method may comprise verifying, at the second node, that the connection request is authorized by the first local policy for the destination port.

A. In certain embodiments, for example, the method may further comprise transmitting an encrypted identifier for the first local policy from the first node to the second node, processor, or computing device.

B. In certain embodiments, for example, the verifying may comprise consulting the first local policy and a second local policy, the second local policy consulted to verify that a second user application is authorized to receive the data at the destination port. In certain embodiments, for example, the first local policy may comprise an n-tuple filter. In certain embodiments, for example, the first local policy may comprise a port-to-port mapping of authorized connection between the first node and the second node, processor, or computing device. In certain embodiments, for example, the authorized port-to-port mapping may comprise an authorized first user-application identifier, an identifier for a second user application authorized to receive the data at the destination port authorized, and a data type identifier.

Certain embodiments may provide, for example, a method for secure communication between applications on two nodes, comprising: i) intercepting, at a first node, a network connection request from a resident first user-application to send data to a destination port on a second node; ii) consulting a first local policy on the first node to verify that the first user-application is authorized to send data to the destination port; and iii) verifying, at the second node, that the connection request is authorized by the first local policy for the destination port.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations. In certain embodiments, for example, the communication management operations may comprise performing communication processing functions on all port-to-network communications of the plurality of processor nodes. In certain embodiments, for example, the communication processing functions may comprise receiving data packets from a user-application source port, the data packets having payloads and associated destination port numbers. In certain embodiments, for example, the communication processing functions may comprise assembling packet segments for all received data packets from the user-application, the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor.

A. In certain embodiments, for example, the communication processing functions may comprise verifying that the source ports are authorized to communicate with ports having the associated destination port numbers.

B. In certain embodiments, for example, the communication processing functions may comprise requesting transmission of network packets to the network, each one of the network packets comprising a port number of one of the associated destination port numbers and one of the assembled packet segments.

C. In certain embodiments, for example, the communication processing functions may comprise requesting transmission of network packets to the network through encrypted communication pathways.

D. In certain embodiments, for example, each one of the encrypted communication pathways may have a one-to-one correspondence with one of the associated destination port numbers.

E. In certain embodiments, for example, the receiving may occur in a kernel of the computing device.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the computing device to perform communication management operations, the communication management operations comprising: performing communication processing functions on all port-to-network communications of the plurality of processor nodes, the performing communication processing functions comprising: i) receiving data packets from a user-application source port, the data packets having payloads and associated destination port numbers; and ii) assembling packet segments for all received data packets from the user-application, the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor.

Certain embodiments may provide, for example, a distributed method to manage communications between plural nodes coupled to a network. In certain embodiments, for example, the distributed method may comprise authorizing port-to-port connections, comprising: obtaining port numbers, node identifiers, user-application identifiers, and payload data type descriptors from pre-provisioned configuration files present on at least two computing devices of the plural computing devices. In certain embodiments, for example, the distributed method may comprise restricting network communications to and from at least one of the at least two computing devices to the authorized port-to-port connections.

Certain embodiments may provide, for example, a distributed method to manage communications between plural nodes coupled to a network, comprising: i) authorizing port-to-port connections, comprising: obtaining port numbers, node identifiers, user-application identifiers, and payload data type descriptors from pre-provisioned configuration files present on at least two computing devices of the plural computing devices; and ii) restricting network communications to and from at least one of the at least two computing devices to the authorized port-to-port connections.

Certain embodiments may provide, for example, a method for secure network communication, comprising: i) selecting, from a preconfigured, exclusive list of authorized data pathways, a dedicated data pathway extending from a source port on a first node to a destination port on a second node, the selected data pathway characterized by a tunnel port number exclusive to the destination port; ii) instantiating a network tunnel extending from the first node to a tunnel port present on the second node, the tunnel port having the selected tunnel port number; iii) prior to transmitting any data from the source port to the destination port: verifying, at the first node, that a first n-tuple received from the network tunnel matches an expected value based on the tunnel port number, the first n-tuple comprising: a nonpublic device code for the second node, a user associated with the destination port, an application associated with the destination port, and a data protocol descriptor; and iv) prior to passing a network packet to the destination port: verifying, at the second node, that an second n-tuple obtained from the network packet matches an expected value based on the tunnel port number, the second n-tuple comprising: a user associated with the source port, an application associated with the source port, and the data protocol descriptor.

Certain embodiments may provide, for example, a method for secure network communication, comprising: i) selecting, from a preconfigured, exclusive list of authorized data pathways, a dedicated data pathway extending from a source port on a first node to a destination port on a second node; ii) instantiating a network tunnel for exclusive use by the dedicated data path, the network tunnel extending from the first node to the second node; iii) prior to transmitting any data through the network tunnel, verifying that the first node, the second node, a user associated with the source port, an application associated with the source port, a user associated with the destination port, an application associated with the destination port, and a data protocol of the data match parameters of the dedicated data path; followed by iv) prior to passing a network packet to the destination port: verifying, at the second node, that the user associated with the source port, the application associated with the source port, and the data protocol descriptor match parameters of the dedicated data pathway.

Certain embodiments may provide, for example, a method of securely transmitting data, comprising: i) prior to transmitting data packets via a dedicated data pathway extending from a source port on a first node to a destination port on a second node, receiving a series of codes at the first node via the dedicated data path; ii) verifying that the received codes include expected codes for the data path, the expected codes associated with the second node, a specified data type, and an owner of the destination port; iii) verifying that the data packets contain expected codes associated with the specified data type and an owner of the source port; followed by iv) passing the data packets to the destination port.

Certain embodiments may provide, for example, a method of securely transmitting data, comprising: i) establishing a dedicated data pathway between a source port on a first node and a destination port on a second node, the destination port associated with an executing user-application configured to receive a specified data type; ii) receiving a series of codes at the first node via the dedicated data path; iii) verifying that the received series of codes include expected codes associated with the second node, the specified data type, and the user-application; followed by iv) transmitting data packets via the dedicated data pathway to the second node; v) further verifying that the transmitted data packets contain expected codes associated with the specified data type and an owner of the source port; followed by vi) passing the transmitted data packets to the destination port. In certain embodiments, for example, the transmitted data packets may be exclusive of the destination port number.

Certain embodiments may provide, for example, a method of securely transmitting data, comprising: i) assembling data packets at a first node, each one of the data packets comprising: a) plural identifiers encoded in metadata; and b) payload obtained from a user-application executing on the source node; ii) passing the assembled data packets to a second node via a dedicated data pathway, the data pathway comprising a source port associated with the user-application; iii) verifying that the metadata identifies a data type and a user-application expected based on a destination port associated with the destination address of the data packets; followed by iv) passing the data packets to the destination port. In certain embodiments, for example, the assembled data packets passed to the second node may be exclusive of the destination port number.

Certain embodiments may provide, for example, a method for secure communication. In certain embodiments, for example, the method may comprise receiving a first network packet from a first user-application, the first network packet comprising a destination port number and a payload. In certain embodiments, for example, the method may comprise forming a second network packet comprising the payload, the second network packet not comprising the destination port number. In certain embodiments, for example, the method may comprise transmitting the second network packet via a machine-to-machine network. In certain embodiments, for example, the method may comprise processing the transmitted second network packet to form a third packet comprising the destination port number and the payload. In certain embodiments, for example, the method may comprise transmitting the payload to a second user-application, the second user-application having a destination port assigned thereto, the destination port number assigned to the destination port.

Certain embodiments may provide, for example, a method for secure communication, comprising: i) receiving a first network packet from a first user-application, the first network packet comprising a destination port number and a payload; ii) forming a second network packet comprising the payload, the second network packet not comprising the destination port number; iii) transmitting the second network packet via a machine-to-machine network; and iv) processing the transmitted second network packet to form a third packet comprising the destination port number and the payload.

Certain embodiments of the presently disclosed methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus may provide, for example, improvements to existing computing technology for packet-based network communications. Internet protocols allow open access for computer users to remotely access other computers and information stores easily from any access point, resulting in many points of attack for malware. While security layers have been added on top of this core architecture, modern malware exploits gaps in these layers through flaws in software and imperfect trust relationships between communicating devices. The improvements of the present disclosure include the following embodiments.

Certain embodiments may provide, for example, a method for network communication between a first computing device and a second computing device and comprising establishing a communication pathway between a first software port of the first computing device and a second software port of the second computing device according to UDP or TCP, the improvement comprising: i) sending a nonpublic first identification code for the first computing device to the second software port via the established communication pathway; ii) receiving, in response to the sending, a nonpublic second identification code for the second computing device at the first software port; and iii) comparing the nonpublic second identification code with a pre-established value for the second computing device.

Certain embodiments may provide, for example, a method for network communication comprising establishing communication pathways according to UDP or TCP, the improvement comprising: i) intercepting network connection requests having associated destination port numbers; ii) identifying predefined communication port numbers, comprising identifying at least one predefined communication port number for each associated destination port number of the associated destination port numbers; iii) sending UDP or TCP connection request packets comprising the predefined communication port numbers, each one of the communication pathways having a one-to-one correspondence with one of the predefined communication port numbers; and iv) authorizing the communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received the communication pathways with predefined authorization codes.

Certain embodiments may provide, for example, a method for network communication comprising establishing communication pathways according to UDP or TCP, the improvement comprising: i) intercepting network connection requests from source ports, the requests having associated destination port numbers; ii) verifying that the source ports are authorized to communicate with ports having the associated destination port numbers; iii) sending a UDP or TCP connection request packets comprising the associated destination port numbers; and iv) authorizing the communication pathways, comprising comparing computing device identifiers, user-application identifiers, and payload data-type identifiers received from the communication pathways with predefined authorization codes.

Certain embodiments may provide, for example, a method for network communication comprising transmitting UDP or TCP network packets through communication pathways, the improvement comprising: i) receiving data packets having payloads and associated destination port numbers; ii) identifying predefined port numbers, each one of the predefined port numbers having a one-to-one correspondence with one of the associated destination port numbers; iii) assembling packet segments, each one of the packet segments comprising one of the payloads, an associated user-application identifier, and a payload data type descriptor; and iv) requesting transmission of UDP or TCP network packets through the communication pathways, each one of the network packets comprising a port number of one of the predefined port numbers and one of the assembled packet segments, each one of the communication pathways having a one-to-one correspondence with one of the predefined port numbers.

Certain embodiments may provide, for example, a method for network communication comprising receiving UDP or TCP network packets from communication pathways, the improvement comprising: i) obtaining destination port numbers, metadata, and payloads associated with UDP or TCP network packets; ii) identifying predefined authorization codes associated with the destination port numbers, each one of the predefined authorization codes comprising a predefined user-application identifier and a predefined payload data-type identifier associated with one of the destination port numbers; iii) authorizing the network packets, comprising: comparing at least a portion of the metadata with the predefined authorization codes; and iv) requesting transmission of payloads from the authorized network packets to destinations referenced by the destination port numbers.

Certain embodiments may provide, for example, a method for network communication between a first computing device and a second computing device and comprising establishing a communication pathway between a first software port of the first computing device and a second software port of the second computing device according to UDP or TCP, the improvement comprising: one or more of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of any of the embodiments disclosed herein.

Certain embodiments, for example, may comprise a product for securing communications of a plurality of networked computing devices. In certain embodiments, for example, the product may comprise a non-transitory computer-readable storage medium having computer-readable program code embodied therein. In certain embodiments, for example, the computer-readable program code may be executable (or program code compilable, linkable, and/or loadable to be executable) by a first computing device (for example a computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)) to enable and/or cause the first computing device to perform communication management operations. In certain embodiments, for example, the communications management operations may comprise receiving a first network packet from a first user-application, the first network packet comprising a destination port number and a payload. In certain embodiments, for example, the communications management operations may comprise forming a second network packet comprising the payload, the second network packet not comprising the destination port number. In certain embodiments, for example, the communications management operations may comprise transmitting the second network packet to network security software on a second computing device. In certain embodiments, for example, the communications management operations may comprise confirming that the network security software is preconfigured to transmit the payload to a second user-application on the second computing device, the second user-application having a destination port assigned thereto, the destination port number assigned to the destination port.

A. In certain embodiments, for example, the first user-application may be resident on the first computing device. In certain embodiments, for example, the network security software may obtain the destination port number from a preprovisioned file, the preprovisioned file resident on nonvolatile storage media in communication with the second computing device.

Certain embodiments may provide, for example, a product for managing communications of a plurality of networked computing devices, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a first computing device executing an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system) to enable and/or cause the first computing device to perform communication management operations, the communication management operations comprising: i) receiving a first network packet from a first user-application, the first network packet comprising a destination port number and a payload; ii) forming a second network packet comprising the payload, the second network packet not comprising the destination port number; iii) transmitting the second network packet to network security software on a second computing device; and iv) confirming that the network security software is preconfigured to transmit the payload to a second user-application on the second computing device, the second user-application having a destination port assigned thereto, the destination port number assigned to the destination port.

A. In any of the products disclosed herein for use on a computing device (for example products for managing communications), the product or a portion thereof may be distributed separately (for example on separate non-transitory computer-readable storage media) from at least a portion (for example all) of an operating system or kernel running (or to be run) on the computing device. In certain embodiments, for example, the product or a portion thereof may be installed separately from at least a portion (for example all) of an operating system or kernel running (or to be run) on the computing device. In certain embodiments, for example, the product or a portion thereof may be compiled separately from at least a portion (for example all) of an operating system or kernel running (or to be run) on the computing device. In certain embodiments, for example, the product or a portion thereof is linked separately from at least a portion (for example all) of an operating system or kernel running on the computing device. In certain embodiments, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein (for example one or more of the establishing, performing, intercepting, identifying, requesting, authorizing, verifying, receiving, assembling, requesting transmission, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, or forming operations or functions disclosed herein) are distributed on separate non-transitory computer-readable storage media from computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform the other of the communication management operations and/or processing functions. In certain embodiments, for example, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting may be distributed on separate non-transitory computer-readable storage media from the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform other communication management operations and/or processing functions disclosed herein.

B. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting and/or the receiving operations or functions on a computing device may be distributed separately (for example on separate non-transitory computer-readable storage media) from computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform one or more of the identifying, authorizing, verifying, assembling, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, and forming operations or functions. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting and/or the receiving operations or functions may be installed separately from computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform one or more of the identifying, authorizing, verifying, assembling, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, and forming operations or functions. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting and/or the receiving operations or functions may be compiled separately from computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform one or more of the identifying, authorizing, verifying, assembling, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, and forming operations or functions. In certain embodiments, for example, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform intercepting and/or the receiving operations or function may be linked separately from computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by the computing device to perform one or more of the identifying, authorizing, verifying, assembling, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, and forming operations or functions.

C. In certain embodiments, for example, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel of the computing device.

D. In certain embodiments, for example, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be agnostic as to the operating system or kernel running on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may contain only a minimum interface functionality required to communicate with an operating system or kernel running on the computing device, and be otherwise agnostic as to the operating system or kernel running. In certain further embodiments, for example, the minimum interface functionality may comprise a kernel header, a definition file, a variable definition, mandatory kernel call, or a combination of two or more of the foregoing. In certain further embodiments, for example, the minimum interface functionality may be limited to one or more kernel headers, one or more definition files, one or more variable definitions, one or more mandatory kernel calls, or a combination of two or more of the foregoing. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be exclusive of any portion of code of a pre-existing operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be exclusive of any calls to functions or modules of a pre-existing operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device.

E. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may receive data from an end-user application program via an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not receive any further data from an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not receive any further data from an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein (for example all of communication management operations and/or processing functions disclosed herein) may not share any address space (for example kernel address space) with an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not use and/or manipulate any operating system or kernel data structure on the computing device.

F. In certain embodiments, for example, at least a portion of computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not be subject to a copyleft license. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not be subject to a copyleft license. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not be subject to a General Public License (GPL), for example the GPL version 1, the GPL version 2, the GPL version 3, a Lesser GPL, or a modified GPL. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not be subject to a Berkeley Software Distribution (BSD) license, for example a BSD License version 2.0, a Revised BSD License, a New BSD license, a Modified BSD License, or an otherwise modified BSD license.

G. In certain embodiments, for example, at least a portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device (for example a portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device that may not be subject to a copyleft license) may be in communication with (for example may be linked to and/or may exchange data with) software that may be subject to a copyleft license (for example software that may be subject to the GPL version 2). In certain embodiments, for example, the software that may be subject to a copyleft license may be part or all of a kernel or an operating system or kernel. In certain embodiments, for example, the software that may be subject to a copyleft license may be an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system) or kernel. In certain embodiments, for example, the software that may be subject to a copyleft license may be at a boundary (or edge or periphery) of the kernel (for example the software that may be subject to a copyleft license may be an API such as a network API). In certain embodiments, for example, the software that may be subject to a copyleft license may be an interoperability interface (for example an interface for communication between at least a portion of a kernel running on the computing device and an application running on the computing device.

H. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may not comprise part of an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel of the computing device, for example in a privileged processing space, while not comprising part of an operating system or kernel executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be executable (or compilable, linkable, and/or loadable to be executable) in an application space of the computing device.

I. In certain embodiments, for example, a portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel space of the computing device, and a further portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device may be executable (or compilable, linkable, and/or loadable to be executable) in an application space of the computing device. In certain embodiments, for example, a portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel space of the computing device, and a further portion of the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device may not be executable (or compilable, linkable, and/or loadable to be executable) in the kernel space (for example it may be executable in the application space or other non-privileged or non-priority executable space).

J. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting and/or the receiving operations or functions may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel space of the computing device, and computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the assembling, requesting transmission, encrypting, decrypting, inserting, translating, comparing, further comparing, and additionally comparing operations or functions may be executable (or compilable, linkable, and/or loadable to be executable) in an application space of the computing device. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform the intercepting and/or the receiving operations or functions may be executable (or compilable, linkable, and/or loadable to be executable) in a kernel space of the computing device, and computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the assembling, requesting transmission, encrypting, decrypting, inserting, translating, comparing, further comparing, and additionally comparing operations or functions may not be executable (or compilable, linkable, and/or loadable to be executable) in the kernel space.

K. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a plug-in. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be present in a library (for example in a dynamic-link library). In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a loadable module. In certain embodiments, for example, the loadable module may be loaded by a computing device during bootup of the computing device. In certain embodiments, for example, the loadable module may be loaded by a computing device prior to loading of an operating system (for example may be loaded by an initial runtime environment or loaded by a Basic Input/Output System (BIOS)). In certain embodiments, for example, the loadable module may be loaded by the computing device after bootup of the computing device. In certain embodiments, for example, the loadable module may be loaded by the computing device during runtime. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a loadable kernel module. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a loadable application module. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a driver.

L. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be dynamically linkable (for example may be a dynamically linkable module, such as a dynamically linkable loadable module). In certain embodiments, for example, the computer-readable program code may be dynamically linkable with a kernel (for example with a Linux or Linux-based kernel). In certain embodiments, for example, the computer-readable program code may be dynamically linkable with an operating system or kernel (for example with an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)). In certain embodiments, for example, references (for example symbol tables, module names, memory offsets, etc.) to the dynamically linkable program code may be stored in a kernel space of the computing device. In certain embodiments, for example, references to the dynamically linkable program may be stored in an application space of the computing device. In certain embodiments, for example, the computer-readable program code may be compiled separately from an operating system or a kernel to form a kernel loadable module. In certain embodiments, for example, the kernel loadable module may be dynamically linked with the kernel during runtime on the computing device.

M. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be linkable (for example dynamically or statically linkable). In certain embodiments, for example, the computer-readable program code may be linkable in a kernel (for example with a Linux or Linux-based kernel). In certain embodiments, for example, the computer-readable program code may be linkable with an operating system (for example with an operating system (for example a Linux operating system, a Linux-based operating system, a real time operating system, a mini-operating system, an edge device operating system, and/or an open source operating system)). In certain embodiments, for example, the computer-readable program code may be linkable (for example dynamically or statically linkable) to an application program. In certain embodiments, for example, the computer-readable program code may be linkable (for example dynamically or statically linkable) to an interface (for example an interoperability interface). In certain embodiments, for example, the computer-readable program code may be linkable (for example dynamically or statically linkable) to an interface between an application space of the computing device and a kernel space of the computing device. In certain embodiments, for example, the computer-readable program code may be linkable (for example dynamically or statically linkable) to an application-to-kernel program interface (for example an interface such as Netlink or Netlinks). In certain embodiments, for example, computer-readable program code may be linkable (for example dynamically or statically linkable) to an application-to-application program interface. In certain embodiments, for example, computer-readable program code may be linkable (for example dynamically or statically linkable) to a kernel-to-kernel program interface.

N. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a statically linkable module. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be a standalone program.

O. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be an object file. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be compilable ASCII code. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the communication management operations and/or processing functions disclosed herein may be compiled.

P. In certain embodiments, for example, computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform intercepting and/or the receiving operations or functions may be invoked by one or more modified kernel functions (for example by a modified network API function such as bind( ) or connect( )). In certain embodiments, for example, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform intercepting and/or the receiving operations or functions may be invoked by one or more modified kernel functions, and computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the identifying, authorizing, verifying, comparing, further comparing, and additionally comparing, may be part or all of a separate executable (or compilable, linkable, and/or loadable to be executable) code that communicates, via an inter-program interface (for example Netlink or Netlinks), with the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the assembling, encrypting, decrypting, inserting, and translating operations or functions. In certain embodiments, for example, the one or more modified kernel functions may be licensed under the GPL version 2. In certain further embodiments, the computer-readable program code executable (or compilable, linkable, and/or loadable to be executable) by a computing device to perform one or more of the establishing, performing, intercepting, identifying, requesting, authorizing, verifying, receiving, assembling, requesting transmission, encrypting, decrypting, inserting, translating, comparing, further comparing, additionally comparing, obtaining, negotiating, identifying, forming operations or functions may not be licensed under a GPL or a BSD license. In certain embodiments, for example, the modified kernel function may be statically linked with an operating system executable (or compilable, linkable, and/or loadable to be executable) on the computing device. In certain embodiments, for example, the modified kernel function may be dynamically linked with an operating system running on the processor.

Certain embodiments may provide, for example, a computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, enables or causes the computing device to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, further enables or causes the computing device to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device running a Linux operating system, enables or causes the computing device to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computer program product comprising a computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device running an operating system (for example, Linux), further enables or causes the computing device to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, an apparatus, comprising: a processor; and a memory coupled to the processor, wherein the memory comprises instructions which, when executed by the processor, enable or cause the processor to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a system, comprising: one or more processors; a memory coupled to said one or more processors, said memory including a computer useable medium tangibly embodying at least one program of instructions executable by at least one of said one or more processors to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computer program product, comprising: one or more machine-useable storage media; program instructions provided by said one or more media for programming a data processing platform to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, an apparatus comprising: a host operating system comprising an active kernel and an active container; and a processor operable with said active kernel to instantiate instances for active Kernel Loadable Modules (KLMs) for servicing said active container, said active KLM's executable to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a system, comprising: one or more processors; an operating system executing on said one or more processors; memory coupled to said one or more processors, said memory including a computer useable medium tangibly embodying at least one program of instructions executable by at least one of said one or more processors to perform operations to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, logic encoded on one or more non-transitory computer readable media for execution and when executed operable to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, logic encoded on one or more non-transitory computer readable media for execution on one or more processors executing operating system commands, when executed operable to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a computing device, causes the computing device to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computing device comprising: a memory containing machine readable medium comprising machine executable code having stored thereon instructions to perform one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a computer program product to perform one or more of the methods disclosed herein, the computer program product comprising: one or more computer readable storage media; and program instructions stored on the one or more computer readable storage media to perform the one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a non-transitory machine-readable storage medium comprising instructions to provide enhanced communication security of a system comprising a processor operating with a Linux or Linux-based operating system, the instructions executable by the processor one or more of the methods disclosed herein.

Certain embodiments may provide, for example, a distributed system, comprising: i) a first computing device; ii) a first network security file containing first parameters, the first network security file resident on the first computing device; iii) a first copy of a network security software, at least a portion of the first copy configured to operate in a kernel of the first computing device; iv) a second computing device; v) a second network security file containing second parameters, the second network security file resident on the second computing device; vi) a second copy of the network security software, at least a portion of the second copy configured to operate in a kernel of the second computing device; and vii) a dedicated port-to-port encrypted communication pathway between the first copy and the second copy, the first copy configured to receive first codes from the second copy and to compare the first codes with the first parameters, to verify that the first copy is authorized to send information to and/or receive information from a user-process running on the second computing device via the dedicated port-to-port encrypted communication pathway, and the second copy configured to receive second codes from the first copy and to compare the second codes with the second parameters, to verify that the user-process is authorized to send information to and/or receive information from the first copy via the dedicated port-to-port encrypted communication pathway.

A. In certain embodiments, for example, the first codes, the second codes, the first parameters, and the second parameters are isolated (for example not accessible by and/or isolated in memory) from user-applications on the first computing device and the second computing device. In certain embodiments, for example, the first codes may be obtained (for example obtained by the second copy) from the second network security file. In certain embodiments, for example, the second codes may be obtained (for example obtained by the first copy) from the first network security file.

B. In certain embodiments, for example, all but at most one (or at most two, three, 10%, 20%, or 20-75%) of the first codes may be present in only a single record of the second network security file. In certain embodiments, for example, the first codes may form a unique n-tuple (for example the n-tuple may be an at least a 2-tuple, an at least a 3-tuple, an at least a 5-tuple, an at least a 6-tuple, an at least an 8-tuple, an at least a 10-tuple, or an at least a 12-tuple) in the second network security file.

C. In certain embodiments, for example, all but at most one (or at most two, three, 10%, 20%, or 20-75%) of the second codes may be present in only a single record of the first network security file. In certain embodiments, for example, the second codes may form a unique n-tuple in the first network security file. In certain embodiments, for example, the first network security file may be different from the second network security file. In certain embodiments, for example, the first parameters may be different from the second parameters.

Certain embodiments may provide, for example, a distributed system, comprising: i) N plural computing devices, which N is an integer (for example N may be at least 2, at least 3, at least 4, at least 6, at least 10, at least 15, at least 20, at least 50, at least 100, at least 250, at least 1000, at least 10,000, at least 100,000, or N may be at least 1,000,000); ii) N plural network security files containing plural parameters, each one of the N plural computing devices having a different one of the N plural network security files resident thereon; iii) N copies of a network security software, each of the N plural computing devices having one of the N copies of network security software installed thereon and configured to operating in a kernel thereof; iv) dedicated port-to-port encrypted communication pathways among the N copies of network security software, a first copy of the N copies configured to receive first codes from a second copy of the N copies and to compare first codes with first parameters of the plural parameters, to verify that the first copy is authorized to send information to and/or receive information from a user-process via one of the dedicated port-to-port encrypted communication pathways, a second copy of the N copies configured to receive second codes from the first copy and to compare the second codes with second parameters of the plural parameters, to verify that the user-process is authorized to send information to and/or receive information from the first copy via the one of the dedicated port-to-port encrypted communication pathways, the first codes present on at most two of the N plural computing devices, the second codes present only on the at most two of the N plural computing devices, the first parameters present only on the at most two of the N plural computing devices, and the second parameters present only on the at most two of the N plural computing devices.

Certain embodiments may provide, for example, a distributed system, comprising: i) N plural computing devices, which N is an integer; ii) N plural network security files containing plural parameters, each one of the N plural computing devices having a different one of the N plural network security files resident thereon; iii) a series of N groups of communication management operations, each of the N plural computing devices having one of the N groups installed thereon and configured to operating in a kernel thereof; iv) dedicated port-to-port encrypted communication pathways among the N groups, a first group of the N groups configured to receive first codes from a second group of the N groups and to compare first codes with first parameters of the plural parameters, to verify that the first group is authorized to send information to and/or receive information from a user-process via one of the dedicated port-to-port encrypted communication pathways, a second group of the N groups configured to receive second codes from the first group and to compare the second codes with second parameters of the plural parameters, to verify that the user-process is authorized to send information to and/or receive information from the first group via the one of the dedicated port-to-port encrypted communication pathways, the first codes present on at most two of the N plural computing devices, the second codes present only on the at most two of the N plural computing devices, the first parameters present only on the at most two of the N plural computing devices, and the second parameters present only on the at most two of the N plural computing devices.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1: Schematic view of a blockchain having a starting block and a series of transactional blocks.

FIG. 2: Schematic view of a blockchain being assembled.

FIG. 3: Schematic view of a distributed ledger ecosystem.

FIG. 4: Schematic view of a distributed ledger ecosystem in a private cloud with network security software at the periphery of the cloud.

FIG. 5: Schematic view of a distributed ledger ecosystem in a public cloud with network security software running on consensus nodes.

FIG. 6: Schematic view of a blockchain-based voting system.

FIG. 7A: Schematic view of a distributed ledger ecosystem including a smart contract deployment server.

FIG. 7B: Schematic view of a distributed ledger ecosystem with network security software running on a smart contract deployment server and a series of peers.

FIG. 7C: Schematic view of a distributed ledger ecosystem with network security software running on a subscriber and a series of peers.

FIG. 7D: Schematic view of a distributed ledger ecosystem with network security software running on an ordering engine and a series of peers.

FIG. 8: Schematic view of secured communication of encrypted information to a distributed ledger and access to the information by a subscriber.

FIG. 9: Schematic view of transmission of data to a private distributed ledger via an I2P protocol.

FIG. 10: Schematic view of trading brokered though a private distributed ledger maintained by several financial institutions.

FIG. 11: Schematic view secure communication of data among a multicurrency mobile wallet app, a fintech bank, and a distributed ledger.

FIG. 12A: Schematic view of revocation of a trust relationship with a node in a distributed ledger infrastructure due to a policy violation by the node.

FIG. 12B: Schematic view of connection termination in a distributed ledger infrastructure following a policy violation by the node.

FIG. 13: Schematic view of encoding data with an encrypted or unencrypted data provenance parameter in a distributed ledger.

FIG. 14: Schematic view of tracking provenance of data passed across a series of nodes.

FIG. 15: Simplified schematic of a hospital.

FIG. 16: Simplified schematic of an Internet of Things ecosystem.

FIG. 17: Simplified schematic of a smart car ecosystem.

FIG. 18: Simplified schematic of a process-controlled industrial production unit.

FIG. 19: Simplified schematic of a retail banking system.

FIG. 20: Simplified schematic for loan application system.

FIG. 21: Simplified schematic for a cloud computing ecosystem.

FIG. 22: Schematic view of exemplary data flow between nodes coupled to a network.

FIG. 23: Schematic view of an exemplary translated data flow between nodes coupled to a network.

FIG. 24: Schematic view of exemplary network configuration.

FIG. 25: Schematic view of exemplary node transmitting data to a network.

FIG. 26: Schematic view of exemplary node comprising a read-only file.

FIG. 27: Schematic view of exemplary node receiving data from a network.

FIG. 28: Schematic view of gateway server.

FIG. 29: Schematic view of gateway server comprising separation kernel.

FIGS. 30(A-D): A flow chart illustrating exemplary communication management operations that may be associated with a network system in accordance with certain embodiments disclosed herein.

FIGS. 31(A-C): A flow chart illustrating exemplary communication management operations that may be associated with a network system in accordance with certain embodiments disclosed herein.

FIGS. 32(A-C): A flow chart illustrating exemplary communication management operations that may be associated with a network system in accordance with certain embodiments disclosed herein.

FIGS. 33(A-B): A flow chart illustrating exemplary communication management operations that may be associated with a network system in accordance with certain embodiments disclosed herein.

FIG. 34: Flow diagram of secure communication protocol.

FIG. 35: Schematic view of first node having network configuration first data structure.

FIG. 36: Schematic view of second node having network configuration second data structure.

FIG. 37: Schematic view of first node having network configuration third data structure.

FIG. 38: Schematic view of second node having network configuration fourth data structure.

FIG. 39: Schematic view of first node having network configuration fifth data structure.

FIG. 40: Schematic view of second node having network configuration sixth data structure.

FIG. 41: Schematic view of first node having network configuration seventh data structure.

FIG. 42: Schematic view of second node having network configuration eighth data structure.

FIG. 43: Schematic view of exemplary node transmitting data to a network.

FIG. 44: Schematic view of exemplary node receiving data from a network.

FIG. 45: Schematic view of gateway server.

FIG. 46: Schematic view of first node having network configuration ninth data structure.

FIG. 47: Schematic view of second node having network configuration tenth data structure.

DETAILED DESCRIPTION OF THE INVENTION

Certain embodiments may provide, for example, a method, a system, a product (for example a computer program product), a distributed system (for example a distributed computer program), software, middleware, computing infrastructure and/or apparatus (or a combination of two or more of the foregoing) to secure network communications around a distributed ledger, subcomponents and/or ancillary components of a distributed ledger, and/or optional distributed ledger applications (for example a wallet such as a mobile wallet). A distributed ledger is a distributed database that maintains information, e.g., a list of data records, computer program code (for example an executable program such as a smart contract), etc. In certain embodiments, for example, the information may comprise financial information, such as a designated portion of one or more financial accounts. The security of the information maintained within a distributed ledger may be enhanced by the fact that the ledger is distributed across plural nodes, which nodes may be one or more systems, machines, computers, databases, data stores or the like operably connected with one another. In certain embodiments, for example, each of the nodes or multiple nodes may be maintained by different entities. A distributed ledger may works without a central repository or single administrator. One well-known application of a distributed ledger is the public ledger of transactions for cryptocurrencies such as used in Bitcoin. In the case of Bitcoin, the data records recorded in the distributed ledger are enforced cryptographically and stored on the nodes of the distributed ledger.

In certain embodiments, for example, a distributed ledger may provide a number of advantages over traditional databases. In certain embodiments, for example, information may be added to the distributed ledger in blocks, wherein the blocks are added in an ordered sequence (or chain). In certain embodiments, for example, the chain of blocks (i.e., the blockchain) may be maintained to provide a history of the information added to the distributed ledger. In certain embodiments, for example, each added block may store a reproducible signature (for example a hash) indicative of a previous state of the blockchain, whereby any alteration of information in a previously-added block in the blockchain will be detected because the resulting signatures in subsequent blocks would not match previously stored signatures.

In certain embodiments, for example, plural nodes hosting the distributed ledger may reach a consensus regarding the validity of information maintained with a block of the blockchain, e.g., a transaction contained on a transaction ledger, financial information or the like. Additionally, when multiple versions of information exist on the ledger, multiple nodes can converge on the most up-to-date version of the transaction. For example, in the case of a virtual currency transaction, any node within the distributed ledger that creates a transaction can determine within a level of certainty whether the transaction can take place and become final by confirming that no conflicting transactions (i.e., the same currency unit has not already been spent) confirmed by the distributed ledger elsewhere.

In certain embodiments, for example, a distributed ledger may comprise two types of records. The first type of record is the information type, which consists of the actual data stored in the distributed ledger. The second type of record is the block type, which confirms when and in what sequence certain information became recorded as part of the distributed ledger. In certain embodiments, for example, information may be created by participants using the distributed ledger in the normal course of business, for example, when someone sends a resource to another person. In certain embodiments, for example, blocks are created by users known as “miners” who use specialized software/equipment to create blocks. In certain embodiments, for example, nodes in possession of a block of the distributed ledger may communicate with other nodes to validate added information based on a set of rules that are defined by the particular system implementing the distributed ledger. For example, in the case of financial information, such as cryptocurrencies or the like, valid information may be digitally signed, conducted from a valid digital wallet and, in some cases, meet other criteria.

In certain embodiments, for example, a distributed ledger may be decentralized—meaning that a distributed ledger is maintained on multiple nodes of the distributed ledger. One node in the distributed ledger may have a complete or partial copy of the entire ledger or set of information and/or blocks on the distributed ledger. Transactions may be initiated at a node of a distributed ledger and communicated to the various other nodes of the distributed ledger. Any of the nodes can validate information, add the information to its copy of the distributed ledger, and/or broadcast the information, its validation (in the form of a block) and/or other data to other nodes. This other data may include time-stamping, such as is used in financial resource distributed ledgers. Various other specific-purpose implementations of distributed ledgers have been developed. These include distributed domain name management, decentralized crowd-funding, synchronous/asynchronous communication, decentralized real-time ride sharing and even a general purpose deployment of decentralized applications.

In certain embodiments, for example, the distributed ledger may be public (for example a distributed ledger like Bitcoin, Litecoin, Ethereum, Zcash, Monero, Dash, Litecoin, Dodgecoin, or Hyperledger). In certain embodiments, for example, the distributed ledger may be private (for example a distributed ledger like Bankchain, MONAX, or Multichain). In certain embodiments, for example, the ledger may be permissionless (for example a ledger like blockchain). In certain embodiments, for example, the ledger may be permissioned (for example like Hyperledger or PBFT). In certain embodiments, for example, the distributed ledger may be a consortium distributed ledger (for example a ledger like R3, EWF, B3i, or Corda).

Certain embodiments, for example, may take the form of a hardware embodiment (for example one or more of the virtual machines, CPUs, physical storage media, interfaces etc. disclosed in one or more of the REFERENCE APPLICATIONS or a combination of two or more of the foregoing), a software embodiment (for example firmware, resident software, distributed software, micro-code, software implementing one or more of the methods, systems, communication management operations, products, communication management operations, software, middleware, computing infrastructure disclosed in one or more of the REFERENCE APPLICATIONS etc., or a combination of two or more of the foregoing), or an embodiment combining software and hardware aspects. Furthermore, certain embodiments may take the form of a computer program product comprising a computer-usable storage medium having computer-usable program code/computer-readable instructions embodied in the medium.

Unless specified, any suitable computer-usable or computer-readable medium may be utilized for embodiments disclosed herein, inclusive of computer-usable or computer-readable medium disclosed in one or more of the REFERENCE APPLICATIONS. The computer usable or computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (e.g., a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires; a tangible medium such as a portable computer diskette, a hard disk, a time-dependent access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other tangible optical or magnetic storage device. In certain embodiments, for example, the medium may comprise a CLOUD download.

Unless specified, any computer programming language may be used to program code/computer-readable instructions for embodiments disclosed herein, inclusive of computer programming languages disclosed in one or more of the REFERENCE APPLICATIONS. In certain embodiments, for example, the program code/computer-readable instructions may be written in a procedural programming language (for example C), an object oriented, scripted or unscripted programming language such as Java, Perl, Smalltalk, C++ or the like, or a combination of two or more of the foregoing.

Certain embodiments may provide, for example, a method (for example a method comprising a series of operational steps) that may be implemented using computer program instructions executable by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the instructions, which execute by the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the method, inclusive of methods disclosed in one or more of the REFERENCE APPLICATIONS.

The computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions, which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions/acts specified in a method. Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out a certain embodiment.

FIG. 1 schematically depicts a blockchain 100 having a starting block 102 (the so-called “genesis block”) and a subsequent series of transactional blocks (104, 106, and 108). Each transactional block (104, 106, or 108) comprises a transaction (110, 112, or 114, respectively) (for example the transfer of property from one party to another) and a hash value (116, 118, or 120, respectively), the hash value referencing the previous block. The hash value is a piece of ciphertext generated by passing (122, 124, or 126) at least a portion of the text of the previous block through at least one mathematical hash function. The hash values (116, 118, and 120) ensure that a block cannot be altered without causing a mismatch between the contents of the block and the hash values in all subsequent blocks. Moreover, any mismatch should be easy to detect because the at least one mathematical hash function is selected to ensure that even a small change to the content of a block produces a large change in the hash value generated from it. Of note, the hash values make it simple to track and audit the validity of the data, making blockchains much more difficult to hack or falsify.

FIG. 2 is a schematic depiction of exemplary steps required to add transactions to a blockchain. A wallet 204 transmits packet data containing a new transaction to one or more network participants in a blockchain network, each of whom maintains their own copy of a list of new transactions 206 (so-called “unconfirmed transactions”). Each participant may verify the veracity of the new transactions according to a pre-determined set of rules, either in partnership or in competition with other participants, and place the verified new transactions in a new block 208. The new block 208 may be appended to a prior instance of the blockchain 212 containing previously added blocks 214A-E as shown, and the provenance and immutability of the resulting blockchain 216 may be established by including a ciphertext signature 218 in the new block 208, wherein the ciphertext signature 218 is obtained by applying a cipher function (for example a hash or trap door function) constructively to all of the prior instance of the blockchain 212. The participant distributes the resulting blockchain 216 to the other network participants, and the participants apply consensus rules to either accept or reject the blockchain 216. If the blockchain 216 is accepted, it replaces the prior instance of the blockchain 212 and becomes the starting point for appending future blocks.

FIG. 3 is a schematic depiction of a distributed ledger ecosystem configured to process user-originated transactions and smart contracts. Consensus nodes 300A-D communicate among one another to verify transactions, authorize messages that trigger execution of smart contract functions (according to consensus rules), update the distributed ledger with new transactions (according to the consensus rules), and manage copies of a distributed ledger 302A-D. The distributed ledger 302A-D contains transactions, uploaded data, and smart contracts grouped in sequences of blocks. Placement of smart contracts on the consensus nodes 300A-D in the distributed ledger 302A-D enables the smart contracts and their data to be maintained in a persistent state based on the state of the distributed ledger 302A-D, and for transactions initiated by the smart contracts to be authorized based on consensus rules followed by the consensus nodes 300A-D. In an exemplary configuration, the distributed ledger contains copies 304A-D of a first smart contract for distributing trust assets (the trust assets and their ownership recorded in the distributed ledger 302A-D) to beneficiaries and copies 306A-D of a second smart contract for updating a car registry recorded in the distributed ledger 302A-D.

In operation, a user node 308 (for example a node at a law firm) deploys a copy of the first smart contract to a consensus node 300A, which then shares the first smart contract with the other nodes. Once the first smart contract is added to the distributed ledger 302A-D, a node at a bank 310 may send a message to one of the consensus nodes 300B to execute a function of the first smart contract to distribute a quantity of cryptocurrency (or other assets, as defined by the smart contract) to user accounts named in the first smart contract. To trigger the distribution, the consensus nodes 300A-D will independently execute said function and communicate with one another to reach consensus about the correct result.

In another example of the ecosystem in operation, a node 312 at a department of motor vehicles may transmit a message to a consensus node 300A to execute a function of the second smart contract to upload updated car registry information to the distributed ledger 302A-D. The distributed 302A-D ledger is updated once the consensus nodes 300A-D verify the message and reach consensus on the result of said function. A separate node 314 (for example a node at a car dealership or a police department) may send a message with proper authenticating credentials to a consensus node 300D to query and read a portion of the uploaded vehicle registry information from a copy 302D of the distributed ledger.

In addition to the foregoing transactions related to smart contracts, a client wallet 316 (for example a wallet present on a smart phone) may submit a transaction to a consensus node 300C to transfer a quantity of cryptocurrency from one address to another address. Similarly to the previous transactions, prior to executing the transaction and updating the distributed ledger 302A-D, the consensus nodes 300A-D will receive and verify the transaction, followed by reaching consensus on the correct state of the distributed ledger 302A-D.

FIG. 4 is a schematic depiction of an embodiment of the communication management operations applied to a distributed ledger ecosystem in a secure private cloud 400 configured for consensus nodes 402A-D to process user transactions and smart contracts and maintain a distributed ledger 404A-D inside the private cloud 400. Client nodes 406A-E submit messages and/or transactions to the consensus nodes 402A-D via gateway nodes 408A-D positioned at the periphery 410 of the private cloud 400. The consensus nodes 402A-D communicate among one another to verify transactions, authorize messages that trigger execution of smart contract functions (according to consensus rules), update the distributed ledger 404A-D with new transactions (according to the consensus rules), and manage copies of a distributed ledger 404A-D. The messages and/or transactions are transmitted to or from user-applications 412A-E running on the client nodes 406A-E to network security modules 414A-E via an internal pathways 416A-E, and the network security modules 414A-E communicate with the private cloud via negotiated communication pathways 418A-E between the network security modules 414A-E of the client nodes 406A-E and network security modules 420A-D of the gateway nodes 408A-D as shown. The network security modules (414A-E and 420A-D) perform communication management operations to ensure that each communication pathway 418A-E is dedicated solely to communication between two pre-established computing devices (406A and 402A, 406B and 402B, 406C and 402C, 406D and 402D, or 406E and 402A, respectively), two pre-established applications (414A and an application running in consensus node 402A (not shown), 414B and an application running in consensus node 402B (not shown), 414C and an application running in consensus node 402C (not shown), 414D and an application running in consensus node 402D (not shown), or 414E and an application running in consensus node 402A (not shown), respectively), pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, negotiations of the communication pathways 418A-E require each endpoint (a port on one of 414A-E or a port on one of 420A-D, as the case may be) to authenticate and authorize the opposing endpoint's computing device, communicating application, application user, and data type. The network security modules (one of 414A-E or one of 420A-E, as the case may be) perform communication management operations to insert metadata into each network packet traversing the communication pathways 418A-E comprises a network packet containing metadata, the metadata comprising encrypted identifiers for the communicating application, application user, and data type. The gateway nodes 408A-D perform communication management operations to extract the metadata from all incoming network packets received via the communication pathways 418A-E and verify that the identifiers for the sending application (one of 414A-E, as the case may be), application user, and data type match pre-established values assigned to the communication pathways. Messages and/or transactions from verified network packets are communicated to at least one of the consensus nodes 402A-D via network communication pathways 422A-E, as shown. Optionally, the gateway nodes 408A-D may be configured whereby each of the communication pathways 418A-E traverses a different network interface controller from the network communication pathways 422A-E (i.e., each of the gateway nodes 408A-D may have at least a first client-facing network interface controller and a separate at least a second private cloud facing network interface controller).

FIG. 5 is a schematic depiction of an embodiment of the communication management operations applied to a distributed ledger ecosystem in a public cloud 500 configured for consensus nodes 502A-D to process user transactions and smart contracts and maintain a distributed ledger 504A-D in a public cloud 500. Client nodes 506A-E submit messages and/or transactions to the consensus nodes 502A-D, and the consensus nodes 502A-D communicate among one another to verify transactions, authorize messages that trigger execution of smart contract functions (according to consensus rules), update the distributed ledger 504A-D with new transactions (according to the consensus rules), and manage copies of a distributed ledger 504A-D. The messages and/or transactions are transmitted to or from user-applications 508A-E running on the client nodes 506A-E to network security modules 510A-E via an internal pathways 512A-E, and the network security modules 510A-E communicate with network security software 514A-D running in the consensus nodes 502A-D via negotiated communication pathways 516A-E between the network security modules 510A-E of the client nodes 506A-E and network security modules 514A-D of the consensus nodes 502A-D as shown. The network security modules (510A-E and 514A-D) perform communication management operations to ensure that each communication pathway 516A-E is dedicated solely to communication between two pre-established computing devices (506A and 502A, 506B and 502B, 506C and 502C, 506D and 502D, or 506E and 502A, respectively), two pre-established applications (508A and an application running in consensus node 502A (not shown), 508B and an application running in consensus node 502B, 508C and an application running in consensus node 502C, 508D and an application running in consensus node 502D, or 508E and an application running in consensus node 502A, respectively), pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, said communication management operations require each network security software at a first endpoint of one of the communication pathways 516A-E (one of 510A-E or one of 514A-D, as the case may be) to authenticate and authorize the opposing endpoint's computing device, communicating application, application user, and data type. Said communication management operations require each communication traversing the communication pathways 516A-E to comprise a network packet containing metadata, the metadata inserted by the sending network security application (one of 510A-E or one of 514A-D, as the case may be), the metadata comprising encrypted identifiers for the communicating application, application user, and data type. On each consensus node 502A-D, network security software (one of 514A-D, as the case may be) executes communication management operations to extract metadata from all incoming network packets received via the communication pathways 516A-E and verify that the identifiers for the sending application (one of 508A-E, as the case may be), application user, and data type match pre-established values assigned to the communication pathways. Messages and/or transactions from verified network packets are communicated to application software (not shown) on the consensus nodes 502A-D via internal communication pathways (not shown).

Analogously to communications between the client nodes 506A-E and the consensus nodes 502A-D, communications between applications on different consensus nodes 502A-D are passed through the network security software 514A-D on the respective nodes and network packets containing metadata are transmitted via negotiated communication pathways 518A-F between the consensus nodes. The sending network security application (one of 514A-D, as the case may be) at one of the consensus nodes executes communication management operations that insert metadata into each communication traversing the communication pathways 518A-F, the metadata comprising encrypted identifiers for the communicating application on one of the consensus nodes (not shown), application user, and data type. The receiving network security application (one of 514A-D, as the case may be) at the consensus node that receives the network packet (one of 502A-D) executes communication management operations to verify that the identifiers for the sending application (not shown), application user, and data type match pre-established values assigned to the communication pathways. Messages and/or transactions from verified network packets are communicated to application software (not shown) on the receiving consensus node (one of 502A-D) via internal communication pathways (not shown).

FIG. 6 is a schematic depiction of blockchain technology applied to voting. A distributed network of voting machines 600 and 602 connected through the internet is capable of participating in accepting votes and competing to add new blocks to prior instances of the blockchain maintained on a series of nodes 604. The distributed network of voting machines 600 and 602 may include (but are not limited to) desktop PCs, laptops, dummy terminals, mobile computers, smartphones, or PDAs. The voting machines may be produced by different manufacturers or owned by different voting machine equipment providers. Each voting machine follows a common protocol in communicating with the distributed network and solving for new blocks on the one or more blockchains stored in the network. The competition among nodes 604 consists of a race to find a nonce which reduces a numerical output of hash function applied to a candidate block below a threshold value. The first node of the series of nodes 604 to successfully find the nonce wins the competition, and their block becomes the next block in the blockchain. By requiring the race (i.e., the so-called “proof of work”), the risk of fraud is substantially reduced as any one node has a very low likelihood of winning the race to add any particular block. Certain voting machines in the distributed network of voting machines 600 and 602 may be the block competition, which others may be dedicated to broadcasting new votes. Voting data is broadcast to the whole network as it is generated and all voting machines work simultaneously to solve the next block in the blockchain. Voting machines may be grouped into different zones located in separate municipalities with separate races where the voters in one municipality cannot vote in the election of the other municipality. Alternatively the zones may be assigned to separate districts with their own local elections and a larger regional election occurring simultaneously.

FIG. 7A is a schematic depiction of a distributed ledger ecosystem. As shown, the ecosystem includes a smart contract deployment server 700, a subscriber 702, and a distributed ledger fabric 704. The deployment server 700 is responsible for communicating smart contracts for use by the fabric. The subscriber 702 transmits proposed transactions (the transactions comprising reads and/or writes to the distributed ledger) and/or is a consumer of information stored in the distributed ledger. The ecosystem shown is for purposes of illustration, and in practice the ecosystem may include a number of smart contract deployment servers under the control of multiple stakeholders. In addition, in practice the ecosystem may include a number subscribers associated with multiple stakeholders. The fabric 704 includes a series of peers 706A-E as well as an ordering engine 708. The peers 706A-E have several responsibilities in the ecosystem, including: executing smart contracts, endorsing/digitally signing responses to proposed transactions, managing execution of smart contracts, receiving proposed transaction blocks from the ordering engine and communicating the proposed transaction blocks to other peers, performing consensus calculations including verifying endorsements and validating transaction results, maintaining copies 709A-E of the distributed ledger, and delivering transaction results to recipients outside the fabric 704. The ordering engine 708 has a complementary set of responsibilities, including processing all configuration transactions to set up network policies, said policies including assignment of peer responsibilities for execution of smart contracts as a result transaction requests (the transaction requests authorized based on a series of preconfigured authorized transaction channels), processing transactions to generate proposed transaction blocks for consumption by the series of peers.

FIG. 7B is a schematic depiction of an embodiment of the communication management operations applied to the transmission of a smart contract from the deployment server to a subset of the series of peers. As shown, information for a smart contract 710A-C is transmitted from a deployment server 700 to a subset of peers 706A-C in the fabric 704 of the ecosystem, the subset of peers 706A-C selected in accordance with one or more authorized transaction channels predefined in the fabric 704. The information for the smart contract 710A-C is transmitted from a user-application 712 running on the deployment server 700 to a network security software 714 via internal pathways 716A-C and the network security software 714 communicates with network security software 718A-C running in the recipient subset of peers 706A-C via negotiated communication pathways 720A-C between the network security software 714 of the deployment server 700 and network security software 718A-C of the peers as shown. The network security software (714 and 718A-C) execute communication management operations to ensure that each communication pathway 720A-C is dedicated solely to communication between two pre-established computing devices, two pre-established applications, pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, the communication management operations require each endpoint to authenticate and authorize the opposing endpoint's computing device, communicating application, application user, and data type. Prior to transmission of the information for a smart contract 710A-C to the peers 706A-C over the communication pathways 720A-C, the network security software 714 on the deployment server 700 executes communication management operations to encode the information for a smart contract according to a predetermined protocol consistent with the data type. The communication management operations insert metadata into each network packet traversing the communication pathways, the metadata inserted by the sending network security application 714, the metadata comprising encrypted identifiers for the communicating application, application user, and data type. The network security software on peers 706A-C receiving the network packets execute communication management operations to extract the metadata from all incoming network packets received via the communication pathways 720A-C and verify that the identifiers for the sending application 712, application user, and data type match pre-established values assigned to the communication pathway 720A-C. Following verification, the communication management operations reconstitute the encoded information for the smart contract 710A-C from the network packets and decode the information from the predetermined protocol into one or more native formats expected by the receiving application software (not shown) on the peers 706A-C. The decoded information for the smart contract 710A-C is communicated to the receiving application software (not shown) on the peers 706A-C via internal communication pathways (not shown).

By restricting communications to pathways between predetermined pairs of nodes (for example predetermined combinations of the deployment server 700 and one of the peers 706A-E), the communication management operations executed by the network security software 714 and 718A-E collectively prevent a nefarious outside node from arbitrarily installing software on the peers 706A-E (or any other nodes on the fabric such as nodes associated with the ordering engine 708), even if passwords or private keys providing rights to upload smart contracts were to become compromised. In addition, any malware that gains a foothold on the deployment server 700 will be prevented from forming a communication pathway with any of the peers, and therefore is unable to transmit malicious code (for example a malicious smart contract or another instance of malware) to any of the peers 706A-E. In particular, any attempt to form the communication pathway from the malware to the peers will be declined by the network security software 714 when communication management operations ascertain that the malware is not an authorized application, is not authorized to open a port on the deployment server 700, and is not authorized to form a communication pathway with an application port on any of the peers 706A-E. In addition, even if a communication pathway were somehow formed, any malware that does not conform to the predetermined protocol would in short order fail the described encoding and decoding process performed by the communication management operations.

FIG. 7C is a schematic depiction of an embodiment of the communication management operations applied to submitting a proposed transaction to peers and obtaining their endorsement. As shown, a proposed transaction configured to trigger execution of copies of the smart contract 710A-C is originated by a user-application 724 on the subscriber 702 and transmitted to a subset of peers 706A-C in the fabric 704 of the ecosystem via transaction information 722A-C, the subset of peers 706A-C selected in accordance with required endorsements (for example digitally signed responses to the transaction information 722A-C) for the proposed transaction. After receiving the transaction information 722A-C for the proposed transaction, executing the smart contract 710 to obtain a proposed result, and independently accepting the proposed result, the three peers 706A-C signal endorsement of the transaction information 722A-C for the proposed transaction by returning a digitally signed response 726A-C specific to the proposed transaction to the subscriber 702. As but one possible example, a transaction to release funds from an escrow (i.e., record a change ownership of the funds in the digital ledger) may require the endorsement of any two of the three peers 706A-C, wherein each of the three peers 706A-C is associated with a different organization party to the proposed transaction. The transaction information 722A-C for the proposed transaction is transmitted from the user-application 724 to a network security software 728 via internal pathways 730A-C and the network security software 728 communicates with the network security software 718A-C running in the recipient subset of peers 706A-C via negotiated communication pathways 732A-C between the network security software 728 of the subscriber 702 and network security software 718A-C of the peers as shown. The network security software (728 and 718A-C) executes communication management operations to ensure that each of the communication pathways 732A-C is dedicated solely to communication between two pre-established computing devices, two pre-established applications, pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, the communication management operations require each endpoint to authenticate and authorize the opposing endpoint's computing device, communicating application, application user, and data type. Prior to transmission of the transaction information 722A-C for the proposed transaction to the peers 706A-C over the communication pathways 732A-C, the network security software 728 on the subscriber 702 executes communication management operations to encode the proposed transaction according to a predetermined protocol consistent with the data type. The communication management operations executed by the sending network security application 728 further insert metadata into each network packet traversing the communication pathways 732A-C, the metadata comprising encrypted identifiers for the communicating application, application user, and data type. Communication management operations executed by network security software 718A-C at the peers 706A-C extract the metadata from all incoming network packets received via the communication pathways 732A-C and verify that the identifiers for the sending application 724, application user, and data type match pre-established values assigned to the communication pathways 732A-C. Following verification, the communication management operations executed by the network security software 718A-C decode the encoded data in the network packets from the predetermined protocol and reconstitute the proposed transaction into one or more native formats expected by the receiving application software (not shown) on the peers 706A-C. The decoded proposed transaction is communicated to the receiving application software (not shown) on the peers 706A-C via internal communication pathways (not shown). In this schematic depiction, after receipt of the transaction information 722A-C for the proposed transaction from the subscriber 702, the three peers 706A-C signals endorsement of the proposed transaction to the subscriber 702 by transmitting digitally signed responses 726A-C specific to the proposed transaction via the same communication pathways 732A-C.

FIG. 7D is a schematic depiction of an embodiment of the communication management operations applied to the subscriber submitting the transmitting digitally signed responses to the ordering engine as a transaction to be ordered. In a first step, the digitally signed responses are processed by the user-application 724 and a transaction message 734 generated for transmission from the subscriber 702 to the ordering engine 708 as a transaction to be ordered. The transaction message 734 is transmitted from the user-application 724 to the network security software 728 via an internal pathway 736 and the network security software 728 communicates with the network security software 738 running in the ordering engine 708 (i.e., network security software running on one or more ordering engine nodes) via a negotiated communication pathway 740 established by communication management operations between the network security software 728 of the subscriber 702 and the network security software 738 of the ordering engine 708 as shown. The communication management operations assure that the communication pathway 740 is dedicated solely to communication between two pre-established computing devices, two pre-established applications, pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, the communication management operations at a first endpoint of the communication pathway 740 authorize the opposing endpoint's computing device, communicating application, application user, and data type. Prior to transmission of the transaction message 734 to the ordering engine 708 over the communication pathway 740, the network security software 728 on the subscriber 702 execute communication management operations to encode the transaction message 734 according to a predetermined protocol consistent with the data type. The communication management operations executed by the sending network security application 728 insert metadata into each network packet traversing the communication pathway 740, the metadata comprising encrypted identifiers for the communicating application, application user, and data type. The network security software 738 running on the ordering engine 708 executes communication management operations to extract the metadata from all incoming network packets received via the communication pathway 740 and verify that the identifiers for the sending application 724, application user, and data type match pre-established values assigned to the communication pathway 740. Following verification, the communication management operations executed by network security software 738 reconstitute the encoded transaction message 734 and decode the message from the predetermined protocol into one or more native formats expected by the receiving application software on the ordering engine 708. The decoded transaction message 734 is communicated to the receiving application software 744 on the ordering engine 708 via an internal communication pathway 745.

In the second step, the ordering engine 708 processes the transaction message 734 and adds the transaction to a proposed block (which may also include other proposed transactions submitted from other subscribers) and disseminates information for the proposed block 742A-E to the peers 706A-E. The information for the proposed block 742A-E is transmitted from the user-application 744 running in the ordering engine 708 to a network security software 738 via internal pathways 748A-E and the network security software 738 communicates with the network security software 718A-E running in the recipient peers 706A-E via negotiated communication pathways 750A-E between the network security software 738 of the ordering engine 708 and network security software 718A-E of the peers as shown. The network security software (738 and 718A-E) execute communication management operations to ensure that each of the communication pathways 750A-E is dedicated solely to communication between two pre-established computing devices, two pre-established applications, pre-established users for each of the two applications (i.e., a single user for each application), and a pre-established data type. Accordingly, the communication management operations require each endpoint of the communication pathways 750A-E to authenticate and authorize the opposing endpoint's computing device, communicating application, application user, and data type. Prior to the ordering engine 708 disseminating information for the proposed block 742A-E to the peers 706A-E over the communication pathways 750A-E, the network security software 738 on the ordering engine 708 executes communication management operations to encode and then disseminate information for the proposed block 742A-E according to a predetermined protocol consistent with the data type. The communication management operations executed by the sending network security application 738 further inserts metadata into each network packet traversing the communication pathways 750A-E, the metadata inserted by the, the metadata comprising encrypted identifiers for the communicating application, application user, and data type. The network security software 718A-E running on the peers 706A-E executes communication management operations to extract the metadata from all incoming network packets received via the communication pathways 750A-E and verify that the identifiers for the sending application 744, application user, and data type match pre-established values assigned to the communication pathways 750A-E. Following verification, the communication management operations reconstitute the encoded proposed block 742A-E from the network packets and decode the block from the predetermined protocol into one or more native formats expected by the receiving application software (not shown) on the peers 706A-E. The information for the proposed block 742A-E is communicated to the receiving application software (not shown) on the peers 706A-E via internal communication pathways (not shown). Upon receipt of the disseminated information for the proposed block 742A-E, each of the peers 706A-E verifies the required digital signatures according to the endorsement policy, validates transaction results, and updates their respective copy of the distributed ledger 752A-E. Following commitment of the disseminated information for the proposed block 742A-E to the distributed ledger 752A-E, the peers 706A-E will typically act collectively to notify predetermined subscribers (nominally including the subscriber 702) whether the proposed transaction was successfully added to the distributed ledger (or failed). Notification of the predetermined subscribers is performed by network communications using communication pathways negotiated using device-application-user-data type authorizations as described herein.

FIG. 8 schematically depicts an embodiment of the communication management operations applied to secured communication of encrypted data to a distributed ledger mediated by network security software. A first subscriber 800 transmits a network packet to first network security software 802 running on a computing device 804 via a first communication pathway 806. The network packet has a payload 808 comprising an encrypted data 810 portion and a separately encrypted metadata 812 portion. The encrypted data 810 portion of the network packet may be decrypted by communication management operations performed by the first network security software 802 with a cryptographic key, the cryptographic key generated based on cryptographic primitives assigned to the first communication pathway 806. The first network security software 802 executes communication management operations to form unencrypted metadata 814 comprising a public key and index value associated with the cryptographic key. Second network security software 816 on the second computing device 804 executes communication management operations to form a payload 818 comprising the unencrypted metadata 814 and the encrypted data 810, and transmits a network packet containing the payload 818 to a node in a distributed ledger fabric 820 via a second communication pathway 822. The unencrypted metadata 814 and the encrypted data 810 are processed in the distributed ledger fabric 820 and stored in the distributed ledger 824A-D. A second subscriber 826, the second subscriber 826 having authorized access to the cryptographic primitives and permission to access the encrypted data 810 and the unencrypted metadata 814 in its encrypted form in at least a portion 824D of the distributed ledger, obtains the encrypted data 810 and the unencrypted metadata 814 via a third communication pathway 828. The second subscriber 826 may use the public key, index value and cryptographic primitives to reconstruct the cryptographic key and decrypt the encrypted data 810. The first network security software 802 and/or the second network security software 816 may comprise one or more of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein and/or in one of the REFERENCE APPLICATIONS. The first communication pathway 806, the second communication pathway 822, and/or the third communication pathway 828 may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations disclosed herein and/or in one of the REFERENCE APPLICATIONS.

FIG. 9 schematically depicts an embodiment of the communication management operations applied to transmission of data from clients to a private blockchain via an overlay network utilizing one of the protocols disseminated by the Invisible Internet Project (I2P). Client nodes 900A-C submit data to member's 902A-D of an I2P overlay network 902A-K which provide the data to a private blockchain 904. Each communication pathway between and among the client nodes, the overlay network, and the private blockchain may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described above, for example in the discussion of FIGS. 7A-D and 8 and in the REFERENCE APPLICATIONS.

FIG. 10 schematically depicts an embodiment of the communication management operations applied to trading among institutional accounts and a network of financial institutions which also trade among one another. A trader using a first trading workstation 1000 in a first institutional account 1002 engages in a transaction via a first secure communication pathway 1004 with a first financial institution 1006A of a network of financial institutions 1006A-D. The first financial institution 1006A lays off the risk of the first transaction by engaging in a second transaction via a second secure communication pathway 1008 with a second financial institution 1006C which, in turn, lays off the risk of the second transaction by engaging in a third transaction via a third secure communication pathway 1010 with a second trader workstation 1012 at a second institutional account 1014. The first secure communication pathway 1004 is negotiated by communication management operations performed by network security software resident on the first trading workstation 1000 and a server at the first financial institution 1006A. The second secure communication pathway 1008 is negotiated by communication management operations performed by network security software resident on a server at the first financial institution 1006A and a server at the second financial institution 1006C. The third secure communication pathway 1010 is negotiated by communication management operations performed by network security software resident on a server at the second financial institution 1006C and on the second trading workstation 1012. The secure authorized communication pathways (1004, 1008, and 1010) are of the authorized type described above, for example in the discussion of FIGS. 7A-D and 8 and in the REFERENCE APPLICATIONS (i.e., dedicated, preconfigured connections for transmitted data according to a predetermined format between predetermined users and predetermined user processes). Each packet of data received via the secure communication pathways (1004, 1008, and 1010) is inspected by communication management operations performed by the receiving entity (1006A, 1006C, and 1012, respectively) to verify that it is received from an authorized user and application process and is formatted according to an authorized data protocol. The communication pathways (1004, 1008, and 1010) may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations disclosed.

FIG. 11 schematically depicts an embodiment of the communication management operations applied to secure communication of data among a multicurrency mobile wallet app, a fintech bank, and a distributed ledger. A multicurrency mobile wallet app 1100 installed on a mobile device 1102 and lists subaccounts 1104A-D for a public cryptocurrency 1104A, a private cryptocurrency 1104B, a first fiat currency 1104C, and a second fiat currency 1104D. Updated balances for each of the private cryptocurrency, first fiat currency, and second fiat currency subaccounts are provided by a server 1106 at a fintech bank 1108 via a first secured communication pathway 1110 traversing the public internet 1112. Updated balances for the public cryptocurrency sub-account are provided to the wallet app 1100 and to the fintech bank 1108 by queries to a distributed ledger 1114 via a second secure communication pathway 1116 and a third secure communication pathway 1118, respectively. The wallet app 1100 comprises embedded security software which communicates with complementary network security software at the fintech bank 1108 and the distributed ledger 1114 via a series of communication management operations to establish the first and second secure communication pathways (1110 and 1116, respectively). The third secure communication pathway 1118 is established between the fintech bank and the distributed ledger via communication management operations performed by their respective network security software. Each of the three secure communication pathways is a dedicated, preconfigured connections for transmitted data according to a predetermined format between predetermined users and predetermined user processes. Each packet of data received is inspected by the communication management operations performed by the receiving entity to verify that it is received from an authorized user and application process and is formatted according to an authorized data protocol. Each of the communication pathways (1110, 1116, and 1118) may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described above, for example in the discussion of FIGS. 7A-D and 8 and in the REFERENCE APPLICATIONS.

FIG. 12A schematically depicts an embodiment of the communication management operations applied to revocation of a trust relationship with a node in a distributed ledger infrastructure due to a policy violation by the node. Distributed ledger nodes 1200A-D in a distributed ledger infrastructure 1202 and device 1204 are each configured with network security middleware 1206A-D and 1208, respectively, each of which executes communication management operations to process local configuration data to establish relationships among the nodes themselves as well as the network security software. If one of the distributed ledger nodes 1206A becomes infected with malware 1210 which attempts to establish an unauthorized communication pathway 1212 to exfiltrate packet data to an unauthorized remote node 1214. Communication management operations performed on the network security middleware 1206A detect the attempt and prevents formation of the connection pathway 1212. In addition, as the attempt to exfiltrate the data violates the policy of the distributed ledger infrastructure, the network security middleware 1206A notifies the other node's network security middleware 1206B-D via network communication pathways 1216B-D. In addition, nodes 1206B-C notify the device network security middleware 1208 via network communications 1218B-C. The network security middleware 1206A-D and 1208 in turn execute communication management operations to terminate existing connections with the node 1206A and refuse further connections with the node.

FIG. 12B schematically depicts an embodiment of the communication management operations applied to the termination of the connections 1212 and 1216A-C.

FIG. 13 schematically depicts an embodiment of the communication management operations applied to encoding data with an encrypted or unencrypted data provenance parameter in a distributed ledger. Application process 1300 running on node 1302 transmits data 1304 to network security software 1306. The network security software 1306 executes communication management operations to form a network packet 1308 comprising the data 1304 and an encrypted application process identifier 1310 (which may optionally include a data protocol parameter for the data). The network packet 1308 is transmitted to a second node 1312 which it is received by second network security software 1314. The second network security software 1314 executes communication management operations to compare a decrypted form of the process identifier 1310 with an expected predetermined value. If the identifier and the value match, the second network security software 1314 executes communication management operations to concatenate the data 1302 and the process identifier 1310 (optionally either encrypted or unencrypted) and transmit the modified data 1316 in a network packet 1318 to an application 1320 configured to request that the modified data 1316 be encoded in a distributed ledger 1322A-D.

FIG. 14 schematically depicts an embodiment of the communication management operations applied to tracking provenance of data passed across a series of nodes. Information 1400 is processed by a sequence of N+1 nodes 1, 2, 3, . . . , N, N+1 1402A-E. Each of the N nodes processes the information and N network security software 1404A-D insert N encrypted data provenance parameters in a cumulative fashion as shown by 1406A-C into N network packets 1408A-C as shown. The packet 1408C is delivered to network security software 1410 on a node 1402E which executes communication management operations to parse the encrypted parameters contained in the metadata 1406C and consult a configuration file 1412 to determine whether the pathway followed by the data among the N nodes is authorized. In comparison with the foregoing embodiment, a communication path not utilizing the network security software would send data to a destination device without any of the disclosed provenance parameters. As a result, network security software, if any, at the destination device would be unable to determine whether the pathway followed by the data is authorized, including whether the data originated from an unauthorized source application and/or user.

In certain embodiments, for example, one or more nodes selected from the defined groups of networked processor nodes in FIGS. 18-47 may be part of a distributed ledger ecosystem (for example may utilize, interact with, host, or provide ancillary or optional services to a distributed ledger infrastructure), wherein the one or more nodes runs network security software comprising one or more of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus disclosed herein or in one of the REFERENCE APPLICATIONS.

In certain embodiments of the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure, computing infrastructure may be secured by managing network communications (for example, all port-to-network, port-to-port and network-to-port communications) between networked nodes. Communications from user-applications on the network nodes may be managed, transparent to the user-application, by middleware that prevents the user-application from binding directly to a physical interface (or, for example, a virtual interface of a virtual machine). The middleware may operate on multiple nodes to manage outgoing communications from a node (port-to-network), and incoming communications into a node (network-to-port). The middleware may be present on a plurality of network nodes, including, for example, all of the network nodes of a defined group (such as a preconfigured group or a software defined network) to manage encrypted or partially encrypted communications such as tunnel communications (network port-to-network port, or network-to-network). The encrypted or partially encrypted communications such as tunnel communications may be established co-operatively between middleware on two or more network nodes. Authorized network communication may be transacted via these encrypted or partially encrypted communications such as tunnels, which may be dedicated encrypted or partially encrypted communications such as tunnels for authorized communications between a user-application on one network node and a user-application on another network node, processor, or computing device. In addition, the middleware may manage network communication by verifying most data packets (including all or substantially all data packets) resulting from a user-application for transmission over the network complies with a preconfigured, predefined, pre-established and/or preprovisioned set of authentication code parameters (including, for example, one or more of the following: a source user-application identifier, a payload data type descriptor, and port number). Similarly, the middleware may manage network communication by verifying most data packets (including all or substantially all data packets) received from a transmission over the internet for a user-application complies with a preconfigured, predefined, pre-established and/or preprovisioned set of authentication code parameters (including, for example, one or more of the following: a source user-application identifier, a payload data type descriptor, and port number). In such embodiments, the ability for malware to intrude, interrogate and/or proliferate within or among the network nodes is severely thwarted. In certain further embodiments, network communication security may be complemented by computing hygiene policies including human access monitoring and disabling a portion or all USB interfaces on network-accessible devices.

In certain embodiments, for example, the encrypted or partially encrypted communications may comprise a network tunnel. In certain embodiments, for example, the communications are encapsulated public network transmission units that appear to be data. In certain embodiments, for example, the communications may be partially or fully encrypted and transmitted across a network using a network tunnel, wherein the network tunnel may be defined by one or more encryption keys and one or more decryption keys. In certain embodiments, for example, the network tunnel may be defined by a protocol, for example Internet Protocol Security (IPsec), Transport Layer Security (SSL/TLS), Datagraph Transport Layer Security (DTLS), Microsoft Point-to-Point Encryption (MPPE), Microsoft Secure Socket Tunneling Protocol (SSTP), Point-to-Point Protocol (PPP), Layer 2 Tunneling Protocol (L2TP), Multi Path Virtual Private Network (MPVPN), or Secure Shell (SSH) protocol. In certain embodiments, for example, the protocol may require encapsulating a network packet inside another network packet (for example, adding an additional header). In certain embodiments, for example, a network tunnel may be defined by one or more encryption keys and one or more decryption keys associated with the tunnel, exclusive of any additional protocol header.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) among networked nodes in an institution, for example a hospital, a university, a manufacturing facility, etc. In certain embodiments, for example a hospital such as the hospital 1500 schematically depicted in FIG. 15, network security software and configuration data may be employed throughout a defined group of networked processor nodes (for example, all or most of the networked processors at a facility, inclusive of remote facilities) to manage networked communications between workstations, databases, smart devices, communication devices, etc. without requiring pre-existing or new application software to be modified to accommodate the network security software. In the inpatient ward 1502 of FIG. 15, for example, the security software and configuration data is installed on a nurse's station 1504 and smart devices (vital sign monitoring device 1506A, a mobile x-ray machine 1506B, and an infusion device 1506C) in a monitoring zone, which includes private patient suites 1508. In addition, a smart MRI machine 1510 is connected to monitoring systems in another department of the hospital 1500. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

In operation, device software on a smart device generates packet data and requests its transmission to a pre-selected destination port associated with monitoring software at the nurse's station. Rather than sending a data packet directly to the monitoring software, the network security software receives or intercepts the data packet and verifies that the device software is authorized to transmit the data and that the requested destination port of the nurse's station is authorized to receive the payload of the data packet. Next, the network security software repackages the payload of the data packet into a new data packet and assigns the new data packet to an encrypted network tunnel that terminates at a preconfigured port associated with network security software of the nurse's station. This network tunnel is unique to the specific data feed being transmitted by the device, so different data feeds do not share the same tunnel. Prior to forwarding the new data packet to the network, the network security software inserts encrypted metadata into the new data packet defining the device software, the user of the device software, and data type being transmitted.

When the transmitted new data packet is received by the nurse's station, network security software on the nurse's station decrypts and inspects the inserted metadata to verify against a predefined configuration data that the sending device software, user, and data type are authorized for the network tunnel. If so, the network security software extracts the network packet payload and inserts it into a final packet that is forwarded to the destination port of the monitoring software. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the authorized device software, user, and data type used by the network security software to perform authentications.

In a billing department of the hospital, the network security software may be installed on a security server to receive (or intercept) and authorize all data packets received from an insurance provider via the public internet. In cases where a data packet is received from a secure remote node that is cooperatively configured with the security server, the aforementioned steps are applied to the received data packet and the data forwarded to its destination. In cases where the data is received from an unsecured remote node, the security server extracts the payload and processes it into a benign, authenticated format (including steps to render any executable payload inoperable), before forming a new packet for transmission to an endpoint in the hospital network.

While application transparency facilitates deployment of the network security software, in certain environments it is desirable to build applications that directly access a portion of the network security software through a security API. Such applications may be particularly useful, for example, to provide faster data processing and to customize security parameters.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) among networked nodes in a modern hospital. A modern hospital. For example, may occupy several floors of a multistory building and may include hundreds of private patient suites. Through extensive computerization and network connectivity, the patient suites may be grouped into a series of zones, for example, 25-50 suites per zone, which may be monitored by nursing stations dedicated to each zone. Each nursing station may be required to monitor multiple medical data feeds from smart devices (including life support, infusion, x-ray, MRI, kidney dialysis, etc.) located in or near the patient suites and/or other station throughout the hospital and beyond. To meet changing patient requirements, the devices may frequently be relocated to different suites and/or zones, which may require reconfiguration of device assignments among the nursing stations. Embedded processors and network interfaces in the devices may facilitate frequent reconfiguration. Unless secured, hospital networks may be vulnerable because, for example, unsupervised visitors are in frequent close proximity to the smart devices. A bad actor may compromise the network from the privacy of a patient suite, for example by injecting malware into a smart device from a thumb drive (allowing it to spread to other computers and devices in the hospital), by plugging a computer into the network and spoofing the device, or simply by moving the device to a different suite.

In an embodiment, most of the devices, including all, in the hospital network (or portion of the hospital network) may be configured with network security software (middleware) and configuration data to accept network traffic only from (n-tuple) pre-authorized users, pre-authorized applications, pre-authorized devices, and/or pre-authorized data-types. In addition, a separate server may update the configuration data across all zones to reflect reconfiguration events. With the security software running on each device on the network, data transmitted from malware on a smart device is rejected (and an alarm may be sounded) when the malware fails to provide a required user identifier and/or application identifier expected by the network security software. In addition, the network security software may prevent a workstation from connecting to any unauthorized device. When the unauthorized device (whether a new device or a device removed from its allotted zone) attempts to connect, the attempt may be rejected when the unauthorized device failed to provide an expected secret identification code.

Each smart device is may also be protected by installed network security software and configuration data, either installed directly (for devices with sufficient processing capability) or through a legacy adapter (containing the network security software and configuration files) disposed between the device and the network. In addition to the intrusion prevention features noted above, the network security software may also prevent malware resident on a smart device from transmitting data to the network. When the malware attempts to transmit data, the data may be received (or intercepted) and dropped when the network security software detects that the malware is not a pre-authorized application for the smart device.

In addition to the risk of unsupervised visitors, malware may also attempt to penetrate a hospital network through the public Internet, for example through casual browsing, email, or communication with service providers. According to an embodiment, all data packets from the public internet may be passed through a security server before transmitting to any network on the hospital. In cases where the data is received from a secure remote node that is cooperatively configured with the security server, the data may be transmitted to a network in the hospital. In cases where the data is received from an unsecured remote node, the security server takes additional steps to convert data packets into a benign, authenticated format (including steps to render any executable payload inoperable).

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) among networked nodes in an Internet-of-Things application. In an Internet-of-Things application depicted in FIG. 16, for example, a consumer appliance manufacturer equips a suite of processor equipped, wirelessly networked smart products (a refrigerator 1600A, a washing machine 1600B, window shades 1600C, and lighting 1600D) with sensors and preconfigured network security software to securely report authenticated, authorized, encrypted operating data, via routers 1602A-D connected to the public Internet 1604 from homes 1606A-D to the manufacturer's cloud based analytics and maintenance engine 1608. The cloud engine 1608, in turn, utilizes the data to compute performance and/or maintenance parameters, and securely communicates authenticated, authorized control parameter adjustments, maintenance alerts, and/or firmware updates to the smart products 1600A-D. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

For example, upon installation of a smart refrigerator, first network security software in the refrigerator utilizes preconfigured private keys to negotiate an exclusive encrypted network tunnel with second network security software in the cloud engine for the purpose of transmitting time series of temperature and/or temperature set point readings from refrigerator control software, across the public Internet, to cloud engine analytic software. Upon receipt, the analytic software will analyze the data and respond to the control software, for example, with seasonal adjustments to parameters that control operation of the refrigerator's compressor.

Prior to transmission of any readings, the cloud engine and refrigerator control software authenticate the refrigerator-to-cloud data path by exchanging device codes, application (refrigerator control software and/or cloud analytic software) identifiers, and/or data-type identifiers across the encrypted tunnel and verifying that the exchanged values correspond to authorized combinations of values.

Following tunnel authorization, for example, a temperature sensor driver executing on the processor may transmit a time series of temperature readings to the control software that, in turn, sends a request via a network API to transmit the readings in a data packet to a preconfigured destination port of the cloud engine. A first module of the first network security software may receive or intercept the request, uses the destination port number to identify a predetermined tunnel destination port number associated with the second network security software, and verifies that the network tunnel is open. A second module of the first network security software may translate the time series into a lightweight format (for example an MQTT format) for transport. A third module of the first network security software may assemble metadata containing an identifier for the control software, an identifier for the control software process owner, and/or a data protocol for the time series. A fourth module of the first network security software may encrypt the translated time series and the metadata. A fifth module of the first network security software may assemble the encrypted metadata and the encrypted, translated time series to form a network packet for transmission to the tunnel port of the second network security software.

Upon receipt of the network packet, a first module of the second network security software verifies that the network tunnel is open. A second module of the second network security software may decrypt the metadata. A third module of the second network security software may verify that the contents of the metadata match preconfigured, expected values based on the destination tunnel port number. A fourth module of the second network security software may decrypt the translated time series. A fifth module of the second network security software further may translate the translated time series into a format readable by the cloud engine analytic software. A sixth module of the second network security software may insert the properly formatted time series into a new network packet and/or may transmit the new network packet to the analytic software. If the network security software and the analytic software execute on the same processor, the transmittal may use a loopback interface. Otherwise, the new packet may contain appropriate authorization metadata and may be transmitted to the first network security software by a separate encrypted network tunnel to an appropriate device in accordance with the methods described above.

The analytic engine may analyze the time series and may compute updated compressor controller parameters. The new controller parameters may be transmitted to a preconfigured destination port of the refrigerator control software (a different port than the source port used for transmitting the time series discussed above), comprising passing a network packet containing the parameters (and appropriate metadata) across an encrypted network tunnel between the second network security software and the first network security software (a different encrypted network tunnel than the tunnel used to transmit the time series). The methods of forming the connection and moving the data may be in accordance with the methods discussed above. Upon receipt of the updated parameters, the refrigerator control software may update a compressor configuration file(s) referenced by the compressor controller, thereby modifying operation of the refrigerator.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) among networked nodes in a smart transportation ecosystem, for example, network security software and configuration data may be factory installed at a number of attachment points in vehicles, including, for example, dedicated on-board processors for vehicle routing, vehicle data, vehicle communications (for example mobile routers) and vehicle maintenance. A vehicle routing computer, for example, may execute several instances of network security software (in conjunction with configuration data) to ensure the integrity of multiple real-time data feeds received from remote routing servers over a cellular or satellite network, including, for example, weather data, GPS or cellular triangulation data, traffic data, and logistic parameters (for example cargo content, next requested stop, destination location, or delivery status information).

In the smart vehicle ecosystem depicted in FIG. 17, a smart car 1700 receives satellite geopositioning data from a satellite 1702 for processing by an onboard navigation computer equipped with the network security software. A second onboard processor of the smart car 1700 equipped with the network security software receives traffic data broadcasts from a weather bureau 1704 by a cellular data network through a cellular tower 1706. A third onboard processor of the smart car 1700 equipped with the network security software communicates transmission data to a manufacturer's maintenance bureau 1708 and receives periodic firmware updates from the bureau 1708. A fourth onboard processor equipped with the network security software communicates speedometer readings via the cell tower 1706 to a law enforcement vehicle 1710. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

In operation, the network security software may establish discrete encrypted network tunnels configured for each data feed, including verifying the authority of a sending device, application, and/or application user to provide each particular data feed to, for example, the routing software and user by assigned encrypted tunnel. For example, following establishment of one of the encrypted network tunnels, a network security software (or middleware) may receive or intercept incoming network packets at a port defined by the specific encrypted tunnel and extracts data from the packet payload at a predetermined location where it expects encrypted metadata. Next, the first network security software may attempt to decrypt the metadata, for example, using an expected cryptographic key (a rotated key for example derived from an elliptic curve-based key exchange algorithm) and to match the decrypted metadata against expected identifiers for the sending application, application user, and/or data type. If the match is successful, the first network security software may extract the network packet payload and may insert it into a final packet which may be forwarded to a predetermined destination port (based on the encrypted tunnel port number) of the routing software.

Additional network security software (or middleware) may authenticate speedometer data for transmission, for example, to a law enforcement resource. In this mode, configuration data may include cryptographic keys shared with law enforcement used for establishing an encrypted network tunnels between the additional network security software and network security software utilized by the law enforcement resource. The additional network security software may receive or intercept a speedometer reading (encoded, for example, in a network packet received via a loopback interface) from speedometer software and may execute operating system commands to determine the identity of the speedometer software and the process owner. The additional network security software may then verify that the speedometer software matches the factory-installed version and is being executed by a pre-authorized user. Next, the additional network security may package the reading into a data packet and may assign the data packet to an encrypted network tunnel that terminates at a preconfigured port associated with the network security software installed at the law enforcement resource. Prior to transmitting the data packet through the network tunnel, the network security software inserts encrypted metadata that identifies the speedometer software, the user of the speedometer software, and data type being transmitted. Upon receipt of the data packet, law enforcement may authenticate the origin of the reading and the type of data, for example, by using the methods described herein.

In each of the foregoing steps, configuration data may be resident on most, for example, all of the attachment points to keep track of, for example, the ports, sending user-applications, receiving user-applications, data types, and/or devices assigned to most, for example, all of the encrypted network tunnels.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) among networked nodes in an Internet-of-Things process controlled manufacturing line. In the manufacturing line depicted in in FIG. 18, quality control devices 1800A and 1800B inspect raw materials and intermediate products. The quality control devices 1800A and 1800B have embedded processors executing network security software, and are in machine-to-machine communication with control systems 1802A and 1802B, respectively, which also execute network security software. The control systems 1802A and 1802B are, in turn, in machine-to-machine communication with a quality control server 1804, which records electronic batch data and provides control parameters to the control systems 1802A and 1802B. Raw materials are passed through a first stage 1806 to form intermediate products, which are passed through a second stage 1808 to form final products. The final products are loaded into shipping boxes by a robot 1810. The robot is in machine-to-machine communication with a logistics server 1812, and each of the robot 1810 and the logistics server are equipped with network security software. The logistics server 1812 obtains product count information and provides loading instructions to the robot 1810. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) for retail banking applications. In certain embodiments, for example retail banking applications such as the private Automated Teller Machine (ATM) network and the wearable payments ecosystem schematically depicted in FIG. 19, configuration data and network security software may be employed (for example in an embodiment of the communication management operations) throughout a defined group of networked processor nodes to manage network communications. In FIG. 19, network security software is installed on an ATM 1900, transaction processing engine 1902, retail customer's bank server 1904, an Automated Clearing House (ACH) server 1906, and cash provider's bank server 1908. In addition, network security software is installed on a wearable computing device 1910 containing an embedded near-field communication chip and on a merchant's payment processing computer 1912. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

In operation, a retail banking customer provides card and pin input to the ATM 1900 to request a cash withdrawal. Device software resident on the ATM 1900 processes the request and generates encrypted packet data containing the customer's transaction information, card number, and pin input and requests its transmission to a pre-selected destination port associated with a remote transaction processing engine 1902. Rather than sending a data packet directly to the remote transaction processing engine 1902, the network security software receives the data packet and verifies that the device software is authorized to transmit the data and that the requested destination port of the remote transaction processing engine 1902 is authorized to receive the payload of the data packet. Next, the network security software repackages the payload of the data packet into a new data packet and assigns the new data packet to a first encrypted network tunnel 1914 that terminates at a preconfigured port associated with network security software of the remote transaction processing engine 1902. The first encrypted network tunnel 1914 is unique to the specific retail transaction being transmitted by the ATM 1900, so different transactions (for example different retail customers, or different transactions by the same customer) do not share the same tunnel. Prior to forwarding the new data packet to the network, the network security software inserts encrypted metadata into the new data packet defining the device software, the retail customer, and the data type being transmitted.

When the transmitted new data packet is received by the transaction processing engine 1902, network security software resident on the transaction processing engine 1902 decrypts and inspects the inserted metadata to verify against predefined configuration data that the sending device software, retail customer, and data type are authorized for the network tunnel. If so, the network security software extracts the network packet payload and inserts it into a new packet that is forwarded to the destination port of the transaction processing engine software. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the authorized device software, authorized device software user, and data type used by the network security software to perform authentications.

The transaction processing engine software processes the payload to identify the retail customer's card network and associated financial institution 1904, and forms a data packet containing the transaction information for transmission to a destination port of software resident on a server of the associated financial institution 1904. Rather than sending the data packet directly to the server of the associated financial institution 1904, network security software resident on the transaction processing engine 1902 receives the data packet and verifies that the transaction processing engine software is authorized to transmit the data and that the requested destination port of the server of the associated financial institution 1904 is authorized to receive the payload of the data packet. Next, the network security software repackages the payload of the data packet into a new data packet and assigns the new data packet to a second encrypted network tunnel 1916 that terminates at a preconfigured port associated with network security software of the server of the associated financial institution 1904. The second encrypted network tunnel 1916 is unique to the port-to-port connection between the transaction processing engine software, the associated financial institution server software, and the data type being transmitted (and optionally the retail customer identity and the specific transaction). Prior to forwarding the new data packet to the network, the network security software inserts encrypted metadata into the new data packet defining the transaction processing engine software, the transaction processing engine software user, and the data type being transmitted.

When the transmitted new data packet is received by the server of the associated financial institution 1904, network security software resident on the associated financial institution server decrypts and inspects the inserted metadata to verify against predefined configuration data that the sending transaction processing engine software, transaction processing engine software user, and data type are authorized for the second network tunnel. If so, the network security software extracts the network packet payload and inserts it into a new packet that is forwarded to the destination port of the associated financial institution software. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the transaction processing engine software, transaction processing engine software user, and data type used by the network security software to perform authentications.

The associated financial institution software memo debits the retail customer's account in a ledger 1918 of the associated financial institution, and forms a data packet containing an authorization for the ATM transaction for transmission though the second encrypted network tunnel 1916 to a destination port of transaction processing engine software. Prior to forwarding the data packet in a network packet to the network, the network security software inserts encrypted metadata into the network packet defining the associated financial institution software, the associated financial institution software user, and the data type being transmitted.

When the transmitted data packet is received by the transaction processing engine 1902 from the second encrypted network tunnel 1916, network security software resident on the transaction processing engine 1902 decrypts and inspects the inserted metadata to verify against predefined configuration data that the associated financial institution software, the associated financial institution software user, and data type are authorized for the network tunnel. If so, the network security software extracts the network packet payload and inserts it into a new packet that is forwarded to the destination port of the transaction processing engine software. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the transaction processing engine software, transaction processing engine software user, and data type used by the network security software to perform authentications.

The associated financial institution software forms a data packet providing an authorization for the ATM transaction for transmission though the first encrypted network tunnel 1914 to a destination port of ATM 1900 device software. Prior to forwarding the data packet in a network packet to the network, the network security software inserts encrypted metadata into the network packet defining the transaction processing engine software, the transaction processing engine software user, and the data type being transmitted.

When the transmitted data packet is received by the ATM 1900 from the transaction processing engine 1902, network security software resident on the ATM 1900 decrypts and inspects the inserted metadata to verify against predefined configuration data that the transaction processing engine software, the transaction processing engine software user, and data type are authorized for the first network tunnel. If so, the network security software extracts the network packet payload and inserts it into a new data packet that is forwarded to the destination port of the ATM 1900 device software. The ATM 1900 device software processes the payload of new data packet authorizing the transaction followed by dispensing cash to the retail customer. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the transaction processing engine software, transaction processing engine user, and data type used by the network security software to perform authentications.

In addition to sending transaction authorization data to the ATM 1900 device software, the transaction processing engine 1902 forms a data packet for transmission to a destination port of ACH server software. Rather than sending the data packet directly to the ACH server 1906, network security software resident on the transaction processing engine 1902 receives the data packet and verifies that the transaction processing engine software is authorized to transmit the data and that the requested destination port of the ACH server software is authorized to receive the payload of the data packet. Next, the network security software repackages the payload of the data packet into a new data packet and assigns the new data packet to a third encrypted network tunnel 1920 that terminates at a preconfigured port associated with network security software of the ACH server 1906. The third encrypted network tunnel 1920 is unique to the port-to-port connection between the transaction processing engine software, the ACH server software, and the data type being transmitted (and optionally the retail customer identity and the specific transaction). Prior to forwarding the new data packet to the network, the network security software inserts encrypted metadata into the new data packet defining the transaction processing engine software, the transaction processing engine software user, and the data type being transmitted.

When the data packet is received by the ACH server 1906, network security software resident on the ACH server 1906 decrypts and inspects the inserted metadata to verify against predefined configuration data that the sending transaction processing engine software, transaction processing engine software user, and data type are authorized for the third encrypted network tunnel 1920. If so, the network security software extracts the network packet payload and inserts it into a new packet that is forwarded to the destination port of the ACH server software.

The ACH server software processes the payload to identify the cash provider's bank server, and forms a data packet containing the transaction information for transmission to a destination port of software resident on cash provider's bank server 1908. Rather than sending the data packet directly to the software resident on cash provider's bank server 1908, the network security software resident on the ACH server 1906 receives the data packet and verifies that the ACH server software is authorized to transmit the data and that the requested destination port of software resident on cash provider's bank server 1908 is authorized to receive the payload of the data packet. Next, the network security software repackages the payload of the data packet into a new data packet and assigns the new data packet to a fourth encrypted network tunnel 1922 that terminates at a preconfigured port associated with network security software of the destination port of software resident on cash provider's bank server 1908. The fourth encrypted network tunnel 1922 is unique to port-to-port connection between the ACH server software, the associated financial institution server software, the cash provider's bank server software, and the data type being transmitted (and optionally the retail customer identity and the specific transaction). Prior to forwarding the new data packet to the network, the network security software inserts encrypted metadata into the new data packet defining the ACH server software, the ACH server software user, and the data type being transmitted.

When the transmitted new data packet is received by the cash provider's bank server 1908, network security software resident on the cash provider's bank server 1908 decrypts and inspects the inserted metadata to verify against predefined configuration data that the sending ACH server software, ACH server software user, and data type are authorized for the fourth encrypted network tunnel 1922. If so, the network security software extracts the network packet payload and inserts it into a new packet that is forwarded to the destination port of the cash provider's bank server software. The associated financial institution software credits the cash provider's bank account. In each of the foregoing steps, the configuration data provides the necessary translation between the encrypted port and the destination port, as well as identifiers for the ACH server software, ACH server software user, and data type used by the network security software to perform authentications.

In addition to dispensing cash at the ATM 1900, portions of the ATM network may also be used to process transactions in a wearable payments ecosystem. A merchant customer may use a wearable computing device 1910 containing an embedded near-field communication chip to transmit credit payment data to a merchant payment processing computer. Network security software resident on the wearable computing device forms a fifth encrypted network tunnel 1924 analogously to the encrypted network tunnels described above and transmits a network packet containing a payment request payload and metadata analogously to the data transmitted through the encrypted tunnels described above. The merchant payment processing computer transmits the payment request data analogously to the ATM 1900 through a sixth encrypted network tunnel 1926, and the transaction processing engine 1902 and the retail customer's bank server function as described above. When the transaction is authorized by the retail customer's bank server 1904, encrypted packet data is transmitted through the network to complete the transaction at the merchant's payment processing computer 1912. In addition, the software resident on the ACH server 1906 transmits instructions to a cash provider's server 1928 to credit the cash provider's account.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) between customers and a service bureau hosting confidential personal data, such as personal identity data (for example social security numbers), financial data, and/or or health data (for example data covered under the Health Insurance Portability and Accountability Act (HIPAA)). In FIG. 20, an applicant for a loan from a bank 2000 may provide personal financial information to a bank representative who inputs the data into the bank's electronic loan underwriting software resident on a bank server 2002. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

The loan underwriting software resident on a bank server 2002 forms a secure connection over the public Internet 2004 according to Hyper Text Transfer Protocol Secure (HTTPS) protocol with a front end server 2006 at a credit bureau 2008 and transmits a request for the bank applicant's credit history. The front end server 2006 is equipped with first network security software which processes the request by extracting network packet payload data and chopping the data to neutralize any embedded malicious executable code. Once the data is chopped, second network security software resident on the front server 2006 forms an encrypted connection with third network security software resident on a database server 2010 of the credit bureau. The second and third network security software authenticate and authorize one another, the front end server 2006 and the database server 2010 devices, and the data protocol. The data protocol authorization requires that communications transmitted from the front end server 2006 to the database server 2010 consist of SQL queries to receive data, and communications transmitted from the database server 2010 to the front end server 2006 consist of data having a predetermined format. The second network security software creates a request for data based on the chopped payload and, upon receipt, passes the data through the HTTPS connection to the bank underwriting software resident on the bank server 2002.

In certain embodiments, for example, the methods, systems, products, communication management operations, software, middleware, computing infrastructure and/or apparatus of the present disclosure may be employed (for example in an embodiment of the communication management operations) to manage network communications (for example, all port-to-network, port-to-port and network-to-port communications) between, as shown in FIG. 21, a local node 2100 and, via the public Internet, 2102, cloud computing services at a server farm 2104. Each communication pathway between and among nodes may be one of the encrypted communication pathways and/or network tunnels managed by one or more of the communication management operations of the authorized type described herein and/or in the REFERENCE APPLICATIONS.

In operation, all communications between the local node 2100 and the cloud computing services are transmitted through a dedicated bare-metal server 2106. The communications are managed by network security middleware present on the local node 2100 and on the dedicated bare-metal server 2106. The network security middleware negotiates an encrypted network tunnel 2108 by mutual authentication of devices based on shared secret device codes, process and process user identifiers on each device, and data protocol for the data being transmitted over the encrypted network tunnels. A different encrypted network tunnel is negotiated for each port-to-port communication, and the sending process, process user, and data protocol are authorized with each packet transmitted.

A communication path 2110 between the dedicated bare-metal server 2106 and virtual machines resident on cloud computing devices 2112 resident in the server farm 2104 are separately secured and are not protected by the above-noted network security middleware.

Certain embodiments may provide, for example, methods, systems, modules, or products for authorized communication, over a network, between plural nodes coupled to the network.

In certain embodiments, for example, the methods, systems, modules, or products may be implemented in hardware (for example may be implemented partially in hardware or entirely in hardware such as an application-specific integrated circuit). In certain embodiments, for example, the hardware may comprise programmable hardware (for example a field-programmable gate array). In certain embodiments, for example, the methods, systems, modules, or products may be implemented in software (for example entirely in software such as firmware, software resident on one or more nodes of the plural nodes, micro-code, etc.). In certain embodiments, for example, the software may be a computer-usable program stored in a computer-readable media (for example one or more of the non-transitory computer-readable storage media described below). In certain embodiments, for example, the methods, systems, modules, or products may be implemented in a combination of hardware and software.

In certain embodiments, for example, the network may comprise all or a portion of the public Internet, a Local Area Network (LAN) (for example a wired LAN, a wireless LAN, of a combination of the two), a Wide Area Network, a Metropolitan Area Network, a Campus Area Network, a Storage Area Network, a Personal Area Network, a System Area Network (or a Cluster Area Network), an Electronic Private Network, a Virtual Private Network (VPN), a Software-Defined Network, a Virtual Network, or a combination (or hybrid) of two or more of the foregoing networks. In certain embodiments, for example, the network may comprise a local area network supporting Ethernet communication over twisted pair cabling interconnected via one or plural switches and one or plural routers. In certain embodiments, for example, the network may comprise a local area network supporting wireless communication (for example wireless communication according to the IEEE 802.11 standard) using one or plural wireless antenna. In certain embodiments, for example, the network may comprise a local area network having an ARCNET, Token Ring, Localtalk, or FDDI configuration. In certain embodiments, for example, the network may comprise a local area network having Internet access. In certain embodiments, for example, the network may be exclusive of Internet access. In certain embodiments, for example, the network may transmit packet data by one or more propagated signals, for example an electrical signal, an optical signal, an acoustical wave, a carrier wave, an infrared signal, a digital signal, or a combination of two or more of the foregoing signals. In certain embodiments, for example, the network may be configured to transmit packet data (for example Ethernet frames) at a rate of at least 25 kilobits per second (Kbps), for example at least 100 Kbps, at least 250 Kbps, at least 500 Kbps, at least 1 million bits per second (Mbps), at least 10 Mbps, at least 25 Mbps, at least 50 Mbps, at least 100 Mbps, at least 250 Mbps, at least 500 Mbps, at least 1 gigabit per second (Gbps), at least 10 Gbps, at least 25 Gbps, at least 50 Gbps, or the network may be configured to transmit packet data at a rate of at least 100 Gbps. In certain embodiments, for example, the network may have a tree topology. In certain embodiments, for example, the network may be a mesh network.

In certain embodiments, for example, the network may connect plural nodes by routers and switches. In certain embodiments, for example, the plural nodes may comprise one or more of a network attached storage, a server (for example a file server, a mail server, a DNS server, a database server, a DHCP server, a VPN server, a VOIP server, an analytics server, or a portion of a cloud), a workstation (for example a desktop computer or a laptop computer), a mobile computing device (for example a smart phone, a smart tablet, or an embedded processor in an automobile), an input/output device (for example a fax machine, a printer, a scanner such as a bar code scanner, or a scanner/copier), a sensor (for example a temperature sensor, a moisture sensor, or a motion sensor), a camera (for example an IP camera), or a geolocation device (for example a Global Positioning System (GPS)-based device or a cellular triangulation device).

In certain embodiments, for example, the network may be a corporate communication network. In certain embodiments, for example, a portion of the plural nodes may be hosted at a corporate headquarters (for example central corporate databases, an email server, or a file backup storage). In certain embodiments, for example, all incoming traffic from the public Internet to the corporate network may be routed through the corporate headquarters. In certain embodiments, for example, a portion of the plural nodes may reside at one or more branch locations removed from the corporate headquarters. In certain embodiments, for example, the portion of the plural nodes may comprise one or more of a workstation or a sensor. In certain embodiments, for example, the one or more branch locations may communicate with the headquarters by a virtual private connection (for example the network may comprise a VPN). In certain embodiments, for example, the network may provide communication to one or plural mobile corporate assets (for example an automobile such as a rental car or a cargo truck). In certain embodiments, for example, the one or plural corporate assets may comprise one or more of an embedded processor and a sensor.

In certain embodiments, for example, the network may provide communication to, from, or within a hospital or a doctor's office. In certain embodiments, for example, the network may connect one or plural resources with databases, computers, devices, and/or sensors located in the hospital or doctor's office. In certain embodiments, for example, the one or plural resources may comprise a data center (for example a local or remote data center). In certain embodiments, for example, the network may comprise a VPN and/or plural LANs (for example a WAN). In certain embodiments, for example, the one or plural resources may comprise a cloud. In certain embodiments, for example, the one or plural resources may be connected to more than one hospital and/or doctor's office. In certain further embodiments, for example, the network may communicate patient records, patient monitoring data (for example real time data for a patient from a heart monitor being transmitted to a nurse's station), telemedicine data, billing and/or reimbursement data, financial data, equipment maintenance data, or a combination of two or more of the foregoing. In certain embodiments, for example, the network may provide communication between one or plural patient rooms and one or plural computing devices at a hospital or a doctor's office location (for example a nurse's station, a doctor's office, a medical supervisor's office, or a smart device (for example a smart phone running an app) used by a healthcare provider), a data hub (for example a local data hub or a data hub connected to the hospital by a private connection or the public Internet), a database, a smart device (for example a smart phone running an app) and/or the one or plural resources. In certain embodiments, for example, the recipient of the communication may be located within a LAN of the hospital or doctor's office. In certain embodiments, for example, the recipient of the communication may be remote from the LAN of the hospital or doctor's office. In certain embodiments, for example, the recipient of the communication may comprise a business partner (for example a service provider such as a billing service provider or a laboratory) of the hospital or doctor's office. In certain embodiments, for example, the communication may comprise sensor data from one or plural sensors in one of the one or plural patient rooms (for example the one or plural sensors may be an oxygen monitoring sensor, a heart monitor, a blood pressure sensor, or a medicine delivery sensor), a scanner (for example a scanner used to scan a barcode on a medicine container, such as a scanner used to scan a two-dimensional barcode in a hospital room), an input/output device (for example a keypad or a smartphone running an app), or a telemedicine device.

In certain embodiments, for example, the network may provide communication with one or plural automobiles (for example the network may provide communication in a smart car ecosystem). In certain embodiments, for example, one or plural devices in an automobile may be wirelessly connected to the Internet. In certain embodiments, for example, the network may provide communication between one or plural law enforcement-controlled devices and one or plural devices (for example a speedometer, a geolocator, or a kill switch) in (or on) the automobile. In certain embodiments, for example, the network may provide communication between one or plural equipment manufacturer interfaces (for example an interface to a web server or a cloud) and one or plural devices (for example a device configured to provide equipment diagnostic information) in (or on) the automobile. In certain embodiments, for example, the network may provide communication between one or plural urban planning agencies and one or plural devices (for example a geolocator or an onboard video camera) in (or on) the automobile. In certain embodiments, for example, the network may communicate weather information from a weather provider to a device (for example an onboard computer executing an autonomous operating system) in (or on) the automobile. In certain embodiments, for example, the network may communicate traffic information (for example traffic congestion information or traffic signal information) to a device (for example an onboard computer executing an autonomous operating system or a global positioning system software) in the automobile. In certain embodiments, for example, the network may communicate logistic information (for example cargo content, next requested stop information, destination location, or delivery status information) between a corporate database and a device in (or on) the automobile. In certain embodiments, for example, the network may communicate vehicle maintenance information (for example an oil change reminder) between a maintenance provider and a device in (or on) the automobile. In certain embodiments, for example, the network may transmit car payload data, car diagnostic data, business data, and/or infrastructure data between one or plural automobiles and a law enforcement agency, an urban planning agency, a weather provider, a traffic provider, a logistics provider, a car maintenance provider, or a combination of two or more of the foregoing.

In certain embodiments, for example, the network may provide communication in a chemical processing facility. In certain further embodiments, for example, the network may provide communication between a Supervisory Control and Data Acquisition (SCADA) system and a plurality of sensors, controllers, logic units, and controllers. In certain embodiments, for example, the network may communicate batch record data generated at one or plural stages of a chemical process.

In certain embodiments, for example, the network may provide communication among one or plural nodes for one or plural dedicated processes (for example one or plural industrial control processes or one or plural IoT applications). In certain further embodiments, for example, the network may provide communication for maintenance of the configuration of communications among the one or plural nodes. In certain embodiments, for example, the network may provide communications from one or plural dedicated processes or devices to a cloud (for example a storage cloud or an analytics engine).

In certain embodiments, for example, the network may provide communication in a factory. In certain embodiments, for example, the network may provide communication in a power station. In certain embodiments, for example, the network may provide communication in an offshore platform. In certain embodiments, for example, the network may provide communication for Automated Teller Machine (ATM) transactions. In certain embodiments, for example, the network may provide communication for credit card transactions. In certain embodiments, for example, the network may provide communication for monitoring IoT devices (for example monitoring IoT devices located in one or plural homes) for a warranty update, a maintenance indication, a service indication, a coupon, a cross-sale advertisement, an up-sale opportunity, or a combination of two or more of the foregoing. In certain embodiment, for example, the network may provide communication for database access (for example communication for access to a credit bureau database). In certain embodiments, for example, the network may provide communication to a DNS server.

In certain embodiments, for example, the network may transmit packets of binary data, signed or unsigned integer data, text (or string) data, or floating point data. In certain embodiments, for example, the network may transmit packets of analog readings (for example readings from an analog sensor). In certain embodiments, for example, the network may transmit packets of digital readings (for example readings from a digital sensor). In certain embodiments, for example, the network may transmit packets of sensor data (such as sensor readings, sensor state data, sensor warranty information, or sensor configuration data). In certain embodiments, for example, the network may transmit packets of voice data. In certain embodiments, for example, the network may transmit packets of image data. In certain embodiments, for example, the network may transmit packets of video data. In certain embodiments, for example, the network may transmit packets containing part or all of a file according to a protocol. In certain embodiments, for example, the file may be an executable file (for example an application program). In certain embodiments, for example, the file may be a parameters file, a data file, or configuration file (for example a file used to configure authorized communications). In certain embodiments, for example, the file may be a binary file (for example a binary file defining authorized communications). In certain embodiments, for example, the protocol may be a File Transfer Protocol (FTP). In certain embodiments, for example, the network may transmit packets of data for a remote control session. In certain embodiments, for example, the network may transmit packets of typed data (for example strongly typed data). In certain embodiments, for example, the network may transmit machine-to-machine communications. In certain embodiments, for example, the network may transmit packets of data objects. In certain embodiments, for example, the data objects may comprise a topic. In certain embodiments, for example, the network may transmit data packets comprising a publication (for example a publication being transmitted from a publisher to one or more subscribers). In certain embodiments, for example, the network may transmit data packets comprising metadata. In certain embodiments, for example, the metadata may comprise a connection state indicator (for example a connection state indicator indicating whether a port-to-port connection is open, closed, or in the process of being established). In certain embodiments, for example, the metadata may comprise a communication authentication parameter (for example a parameter used to authenticate a communicating device, communicating application, or communicating user). In certain embodiments, for example, the metadata may comprise a communication authorization parameter (for example a parameter used to authorize a communicating device, a communicating application, a communicating user, a data type, or a combination of two or more of the foregoing). In certain embodiments, for example, the metadata may comprise a data type or a data protocol parameter.

In certain embodiments, for example, the one or plural nodes may comprise an electronic device configured to send, receive, and/or forward information over the network. In certain embodiments, for example, the electronic device may be (or may host) a communication endpoint. In certain embodiments, for example, the one or plural nodes may comprise a device configured for network packet (for example Ethernet) communication, for example a computer, a computer system, a computing device, an edge device, part or all of a machine, a sensor, a controller, a microcontroller, a server, a client, a workstation, a host computer, a modem, a hub, a bridge, a switch, or a router configured for network packet communication. In certain embodiments, for example, the one or plural nodes may comprise a processor node equipped with a processor configured to process computer instructions. In certain embodiments, for example, the one or plural nodes may comprise a device configured for executing a network stack, for example a computer, a computer system, computing device, an edge device, part or all of a machine, a sensor, a controller, a microcontroller, a server, a client, a workstation, a host computer, a modem, a hub, a bridge, a switch, or a router executing a network stack.

In certain embodiments, for example, the one or plural nodes may comprise an electronic instruction execution system. In certain embodiments, for example, the one or plural nodes may comprise a processor (for example a central processing unit (CPU)), a microprocessor (for example a single-board microprocessor), a programmable processor (for example a field-programmable gate array (FPGA), an application specific integrated circuit (ASIC), or a virtual machine.

In certain embodiments, for example, the CPU may have an x86 architecture. In certain embodiments, for example, the CPU may be a 4-bit processor such as an Intel 4004 processor. In certain embodiments, for example, the CPU may be an 8-bit processor, for example an Intel 8008 processor, an Intel 8080 processor, or an Intel 8085 processor. In certain embodiments, for example, the CPU may be a bit-slice processor, for example a bit-slice processor selected from the Intel 3000 bit-slice processor family. In certain embodiments, for example, the CPU may be a 16-bit processor, for example a processor selected from Intel MCS-86 processor family such as an Intel 8086 processor, an Intel 8088 processor, an Intel 80186 processor, an Intel 80188 processor, or an Intel 80286 processor. In certain embodiments, for example, the CPU may be a 32-bit processor, for example a non-x86 processor such as an iAPX 432 processor, an i960 processor, an i860 processor, or an XScale processor. In certain embodiments, for example, the CPU may be a 32-bit processor, for example an Intel 80386 range processor such as an Intel 80386DX processor, an Intel 80386SX processor, an Intel 80376 processor, an Intel 80386SL processor, or an Intel 80386EX processor. In certain embodiments, for example, the CPU may be a 32-bit processor, for example an Intel 80486 range processor such as an Intel 80486DX processor, an Intel 80486SX processor, an Intel 80486DX2 processor, an Intel 80486SL processor, or an Intel 80486DX4 processor. In certain embodiments, for example, the CPU may be based on a 32-bit Intel P5 microarchitecture, for example an Intel Pentium processor or an Intel Pentium processor with MMX Technology. In certain embodiments, for example, the CPU may be based on a 32-bit P6/Pentium M microarchitecture, for example an Intel Pentium Pro processor, an Intel Pentium II processor, an Intel Celeron processor, an Intel Pentium III processor, an Intel Pentium II Xeon processor, an Intel Pentium III Xeon processor, an Intel Pentium III Coppermine-based Celeron processor, an Intel Pentium III Tualatin-based processor, an Intel Pentium M processor, an Intel Celeron M processor, an Intel Core processor, or an Intel Dual-Core Xeon LV processor. In certain embodiments, for example, the CPU may be based on a 32-bit NetBurst microarchitecture, for example an Intel Pentium 4 processor, an Xeon processor, an Intel Mobile Pentium 4-M processor, an Intel Pentium 4 EE processor, or an Intel Pentium 4E processor. In certain embodiments, for example, the CPU may be 64-bit IA-64 processor, for example an Intel Itanium processor or an Intel Itanium 2 processor. In certain embodiments, for example, the CPU may have a 64-bit NetBurst microarchitecture, for example an Intel Pentium 4F processor, Intel Pentium D processor, Intel Pentium Extreme Edition processor, or an Intel Xeon processor. In certain embodiments, for example, the CPU may have a 64-bit Core microarchitecture, for example an Intel Core 2 processor, an Intel Pentium Dual-Core processor, an Intel Celeron processor, or an Intel Celeron M processor. In certain embodiments, for example, the CPU may have a 64-bit Nehalem microarchitecture, for example an Intel Pentium processor, an Intel Core i3 processor, an Intel Core i5 processor, an Intel Core i7 processor, or an Intel Xeon processor. In certain embodiments, for example, the CPU may have a 64-bit Sandy Bridge/Ivy Bridge microarchitecture, for example an Intel Celeron processor, an Intel Pentium processor, an Intel Core i3 processor, an Intel Core i5 processor, or an Intel Core i7 processor. In certain embodiments, for example, the CPU may have a 64-bit Haswell microarchitecture. In certain embodiments, for example, the CPU may have a Broadwell microarchitecture, for example an Intel Core i3 processor, an Intel Core i5 processor, or an Intel Core i7 processor. In certain embodiments, for example, the CPU may have a Skylake microarchitecture, for example an Intel Core i3 processor, an Intel Core i5 processor, or an Intel Core i7 processor. In certain embodiments, for example, the CPU may have a Kaby Lake microarchitecture. In certain embodiments, for example, the CPU may have a Coffee Lake microarchitecture. In certain embodiments, for example, the CPU may have a Cannonlake microarchitecture. In certain embodiments, for example, the CPU may Intel Tera-Scale processor. In certain embodiments, for example, the node may comprise a microcontroller. In certain embodiments, for example, the microcontroller may be an Intel 8048 microcontroller, an Intel 8051 microcontroller, an Intel 80151 microcontroller, an Intel 80251 microcontroller, or a microcontroller selected from the MCS-96 family of microcontrollers.

In certain embodiments, for example, the CPU may have an ARM architecture. In certain embodiments, for example, the CPU may have an ARMv1 architecture. In certain embodiments, for example, the CPU may have an ARMv2 architecture. In certain embodiments, for example, the CPU may have an ARMv3 architecture. In certain embodiments, for example, the CPU may have an ARMv4 architecture. In certain embodiments, for example, the CPU may have an ARMv4T architecture. In certain embodiments, for example, the CPU may have an ARMv5TE architecture. In certain embodiments, for example, the CPU may have an ARMv6 architecture. In certain embodiments, for example, the CPU may have an ARMv6-M architecture. In certain embodiments, for example, the CPU may have an ARMv7-M architecture. In certain embodiments, for example, the CPU may have an ARMv7E-M architecture. In certain embodiments, for example, the CPU may have an ARMv8-M architecture. In certain embodiments, for example, the CPU may have an ARMv7-R architecture. In certain embodiments, for example, the CPU may have an ARMv8-R architecture. In certain embodiments, for example, the CPU may have an ARMv7-A architecture. In certain embodiments, for example, the CPU may have an ARMv8-A architecture. In certain embodiments, for example, the CPU may have an ARMv8-A architecture. In certain embodiments, for example, the CPU may have an ARMv8.1-A architecture. In certain embodiments, for example, the CPU may have an ARMv8.2-A architecture. In certain embodiments, for example, the CPU may have an ARMv8.3-A architecture.

In certain embodiments, for example, the node may comprise a Digital Signal Processor (DSP) (for example the DSP may be embedded on a CPU or may be connected to a CPU). In certain embodiments, for example, the DSP may be a C6000 series DSP produced by Texas Instruments. In certain embodiments, for example, the CPU may be a TMS320C6474 chip. In certain embodiments, for example, the CPU may comprise a DSP having a StarCore architecture, for example MSC81xx chip produced by Freescale such as a MSC8144 DSP. In certain embodiments, for example, the CPU may comprise a multi-core multi-threaded DSP such as a multi-core multi-threaded processor produced by XMOS. In certain embodiments, for example, the DSP may be a CEVA-TeakLite DSP or a CEVA-XC DSP produced by CEVA, Inc. In certain embodiments, for example, the DSP may be a SHARC-based DSP produced by Analog Devices. In certain embodiments, for example, the DSP may be an embedded DSP, for example a Blackfin DSP. In certain embodiments, for example, the DSP may be based on TriMedia VLIW technology, for example a DSP produced by NXP Semiconductors. In certain embodiments, for example, the DSP may support fixed-point arithmetic. In certain embodiments, for example, the DSP may support floating-point arithmetic.

In certain embodiments, for example, the node may comprise a Graphics Processing Unit (GPU) (for example the GPU may be embedded on a CPU or may be connected to a CPU). In certain embodiments, for example, the GPU may be a gaming GPU such as GeForce GTX produced by nVidia, a Titan X produced by nVidia, a Radeon HD produced by Advanced Micro Devices (AMD), or a Radeon HD produced by Advanced Micro Devices (AMD). In certain embodiments, for example, the GPU may be a cloud gaming GPU such as a Grid produced by nVidia, or a Radeon Sky produced by Advanced Micro Devices (AMD). In certain embodiments, for example, the GPU may be a workstation GPU such as a Quadro produced by nVidia, a FirePro produced by AMD, or a Radeon Pro produced by AMD. In certain embodiments, for example, the GPU may be a cloud workstation such as a Tesla produced by nVidia, or a FireStream produced by AMD. In certain embodiments, for example, the GPU may be an artificial Intelligence cloud GPU such as a Radeon Instinct produced by AMD. In certain embodiments, for example, the GPU may be an automated/driverless car GPU such as a Drive PX produced by nVidia.

In certain embodiments, for example, the CPU may comprise an AMD Am2900 series processor, for example an Am2901 4-bit-slice ALU (1975), an Am2902 Look-Ahead Carry Generator, an Am2903 4-bit-slice ALU, an with hardware multiply, an Am2904 Status and Shift Control Unit, an Am2905 Bus Transceiver, an Am2906 Bus Transceiver with Parity, an Am2907 Bus Transceiver with Parity, an Am2908 Bus Transceiver with Parity, an Am2909 4-bit-slice address sequencer, an Am2910 12-bit address sequencer, an Am2911 4-bit-slice address sequencer, an Am2912 Bus Transceiver, an Am2913 Priority Interrupt Expander, or an Am2914 Priority Interrupt Controller. In certain embodiments, for example, the CPU may comprise an AMD Am29000 series processor, for example, an AMD 29000, an AMD 29027 FPU, an AMD 29030, an AMD 29050 with on-chip FPU, or an AMD 292xx embedded processor. In certain embodiments, for example, the processor may be an AMD Am9080, an AMD Am29X305, or an AMD Opteron A1100 Series.

In certain embodiments, for example, the CPU may be a Motorola 68451, a MC88100, a MC88110, a Motorola 6800 family, a Motorola 6809, a Motorola 88000, a Motorola MC10800, or a Motorola MC14500B processor. In certain embodiments, for example, the CPU may be a Motorola PowerPC processor, for example a PowerPC 600, a PowerPC e200, a PowerPC 7xx, a PowerPC 5000, a PowerPC G4, or a PowerQUICC processor.

In certain embodiments, for example, the one or plural nodes may comprise one or more processors coupled to one or more other components, inclusive of one or more non-transitory memory, one or more user input/output devices (for example a keyboard, a touchscreen, and/or a display), one or more data buses, and one or more physical interfaces to the network. In certain embodiments, for example, the one or more physical interfaces may comprise an Ethernet interface (for example a copper or fiber interface), a wireless interface (for example a wireless interface according to the IEEE 802.11 standard), a wireless broadband interface (for example a “Wi-Max” interface according to the IEEE 802.16 standard), a wireless interface according to an IEEE 802.15.4-based standard (for example an interface according to the Zigbee specification), a Bluetooth interface (for example a Bluetooth interface according to the IEEE 802.15.1 standard), a modem, or a combination of two or more of the foregoing interfaces. In certain embodiments, for example, the one or more physical interfaces may comprise an FPGA programmed for high speed network processing. In certain embodiments, for example, the one or more physical interfaces (for example an Ethernet interface or one of the aforementioned wireless interfaces) may have a data transfer rate of 10 Mbps, 100 Mbps, 1 Gbps, 10 Gbps, or 100 Gbps. In certain embodiments, for example, the one or more physical interfaces may have a data transfer rate of at least 10 Mbps, for example at least 100 Mbps, at least 1 Gbps, at least 10 Gbps, or the one or more physical interfaces may have a data transfer rate of at least 100 Gbps. In certain embodiments, for example, the one or more physical interfaces may have a data transfer rate of less than 100 Gbps, for example less than 10 Gbps, less than 1 Gbps, less than 100 Mbps, or the one or more physical interfaces may have a data transfer rate of less than 10 Mbps.

In certain embodiments, for example, the one or plural nodes may comprise computer-readable media configured to store information (for example data or computer-readable instructions). In certain embodiments, for example, the computer-readable media may comprise non-transitory computer-readable storage media. In certain embodiments, for example, the non-transitory computer-readable storage media may comprise a magnetic disk, an optical disk, random access memory (RAM), read-only memory, a flash memory device, or phase-change memory. In certain embodiments, for example, the non-transitory computer-readable storage media may be a fixed memory device, such as a hard drive. In certain embodiments, for example, the non-transitory computer-readable storage media may comprise one or plural device drives. In certain embodiments, for example, one or plural device drives may be selective from the group consisting of a parallel IDE drive, a serial EIDE drive, a SCSI based drive (for example Narrow, UW, LVD, etc.), an external USB/Flash drive; an IOMEGA Zip drive, a Jazz drive, a CD/DVD, a CD-R/RW, a DVD-R/RW drive, or a combination of two or more of the foregoing device drives. In certain embodiments, for example, the non-transitory computer-readable storage media may be a removable memory device, such as a diskette or a Universal Serial Bus (USB) flash drive. In certain embodiments, for example, the one or plural nodes (for example all of the plural nodes) may be exclusive of removable computer-readable media.

In certain embodiments, for example, the methods, systems, modules, or products may be implemented in software that is stored in one or more of the aforementioned computer-readable media and, when ready to be utilized, loaded in part or in whole (for example, into RAM) and executed by a CPU.

In certain embodiments, for example, the one or plural nodes may communicate (for example internally, or for example with each of another one or more of the plural nodes over the network) using transitory computer-readable communication media. In certain embodiments, for example, the transitory computer-readable communication media may comprise a propagated signal, for example an electrical signal, an optical signal, an acoustical wave, a carrier wave, an infrared signal, and/or a digital signal.

In certain embodiments, for example, the one or plural nodes may comprise an operating system defining a kernel (for example the one or plural nodes may be plural nodes, wherein a first node of the plural nodes comprises a first operating system and a second node of the plural nodes comprises a second operating system, the first operating system the same or different from the second operating system). In certain embodiments, for example, the operating system may be selected from the group consisting of 2K, 86-DOS, A/UX, Acados, ACP (Airline Control Program), AdaOS, ADMIRAL, Adrenaline, aerolitheOS, Aimos, AIOS, AIX, AIX/370, AIX/ESA, Aleris Operating System, Allegro, AllianceOS, Alpha OS, Alto OS, Amiga OS, Amoeba, Amstrad, AMX RTOS, AneedA, AngelOS, Antarctica, AOS/VS, Aperios, Apollo Domain/OS, ApolloOS, Apostle, Archimedes OS, AROS, ARTOS, Asbestos, Athena, AtheOS, AtomsNet, Atomthreads, AuroraOS, AutoSense OS, B-Free, Bada, BAL, Banyan VINES, Basic Executive System, BelA, BeOS, Beowulf, BKY, BlueEyedOS, BOS, BOS1810, BoxOS, bpmk, BPMK, BRiX, BS600, BS2000, BSDi, BugOS, Calmira, CCP (Computer Control Program), CDOS, Cefarix, C Executive, Chaos, ChibiOS, Chimera, Chippewa OS, Choices, Chorus, Cinder OS, Cisco IOS, Clicker32, CMW+(SCO), COBRA, Coherent, CONSENSYS, Contiki, ConvexOS, Cos, Cosy, Counterpoise, CP/K, CP/M, CP/NET, CP/Z, CPF (Control Program Facility), Cromix, Cronus, CSOC, CTOS, CTSS, CX/SX, Cygnus, DAC, Darwin, Data General, DC/OSx, DCP, Degenerate OS, Delitalk, DELL UNIX, Deming OS, DEMOS, DesktopBSD, DESKWORK, DG/UX, DIGITAL UNIX, dingOS, DK/DOS, DLD, DNIX, Domain OS, DOS, DOS2, DOS 50, Dosket, drex, DR-DOS, Drops, Drywell OS, DS-OS, DTOS, DVIX, DYNIX Unix (Sequent), ECL-3211, eComStation, eCos, EduOS, EGOS, ekkoBSD, Elate, ELKS, Elysium, EOS, EP/IX, EPOC, ERaMS, ERIKA, EROS, ESER, ESIX, ESKO, Eumel, EuNIX, Exopc, ExOS, Express, Famos, FDOS, Fiasco, Flamethrower, FlashOS, FlexOS, FlingOS, FLP-80 DOS, Flux, Flux-Fluke-Flask, FMS, Forth, FortiOS, FreeBSD, FreeDOS, FreeDOWS, FreeVMS, Frenzy, Fuchsia, FullPliant, FunatixOS, FxOS, GazOS, GCOS, GECOS, GeekOS, Gemini Nucleus, Genera, GEORGE, GEOS, GM OS, GNU Hurd, GNUstep, Go, Goah, Gould OS, Grasshopper, GUIDE, HA-MSP, Hactar, Harmony, Haïku, Helios, HES, Hive, HOPE, HP-87 OS, HP-UX, HT-11, Hurd, Hurricane, HydrixOS, i5/OS, IBM PC-DOS, IBSYS, Icaros Desktop, ICL Unix, Immunix, Inferno, INMOS, INTEGRITY RTOS, Iridium OS, IRIX, iRMX, IRTS, ISC (Interactive), ISIS, ISSL, ITRON, ITS, JAMB, JavaOS, Jbed, JeniOS, Jeo-OS, Jibbed, JOS, JTMOS, JUNOS, JxOS, KAOS, Kaspersky OS, Katix, Kea, Kerberos, KeyKOS, KolibriOS, KOS, KRONOS, KROS, KRUD, Kylin, L4, L13Plus, LainOS, LAN Manager, LDOS, LegOS, IeJOS, Linux, Lisa OS, LTSS, LynxOS, Mach, Mac OS 8, Mac OS 9, Mac OS X, MANOS, MaRTE OS, Maruti, Masix, Master, Maverick OS, MBOS, MCP (Master Control Program), MDOS, MenuetOS, Merlin, Micriμm, MICRODOS, MicroVMS, MidnightBSD, MikeOS, Minima, Minix, Minoca OS, Minux, Miranda, Miray μnOS, MITE 80/10S, MK++, ML, ModulOS, Monitor, MOPS, MorphOS, MOS, MOSIX, MPE/iX, MPE OS, MRT1700, MS-DOS, MSOS, MT809, Multics, Mungi, MUTOS, muVinix, MVS, Möbius, NachOS, NCR Unix, NEC DOS, NECUX, Nemesis, NeOS, NetBSD, Netware, NewDeal, NEWDOS, NewOS, NEWS-OS, Newton OS, NexentaOS, NeXTStep, NextworksOS, Nexus, Nimbus, NintendOS, Node OS, NOS, NOS/BE, NOS/VE, Nova, Novell DOS, NS/GDOS, NSK, NTDIOS, Nucleus, Oaesis, Oasis, Oberon, Objex, Odin, Omega 4, OnCore, On Time RTOS-32, Opal, OpenBeOS, OpenBSD, OpenDarwin, OpenRavenscar, OpenServer, OpenSolaris, OpenVision, OpenVMS, OppcOS, OS-2, OS-9, OS-C, OS/2, OS/2 Warp, OS/9, OS/360, OS/390, OS/400, OS/ES, OS/M, OS4, osCAN, OSE, OSF/1, Osx, OSx16, OZONE, PAKOS, Palm OS, PAPL, Paramecium, ParixOS, Paros, PaulOS, P BASIC, PC-BSD, PC-DOS, PC-MOS/386, PC/M-System, PDOS, PEACE, Pebble, Pegasos, PETROS, Phantom OS, Phos, PikeOS, PIOS, PizziOS, Plan 9, Plex86, PM_SZ_OS, PocketPC 2003, PowerMAX, PowerOS, PowerSX, PowerUX, ProDOS, Prologue, Proolix, ProOSEK, PSOS, pSOSystem, PSU, PTS DOS, PublicOS, PURE, QDOS, QNX, Quadros, RadiOS, RBASIC, RCOS, RCOSjava, RDOS, ReactOS, REAL-32, Realogy Real Time Architekt, REBOL-IOS, Redox, ReWin, REX-80/86, REXX/OS, RHODOS, RISC OS, RMOS, RMS 68k, Roadrunner, Rocket, Rome, ROME, RSTS/E, RSX-11, RT-11, RTEL, RTEMS, RT Mach NTT, rtmk, RTMX, RTOS-32, RTOS-UH, RTS-80, RTX, RTXDOS, RxDOS, S.Ha.R.K, Sanos, SCO OpenServer, SCOPE, ScorchOS, ScottsNewOS, Scout, SCP, SCP (System Control Program), SCP-IBE, Self-R, SeOS, Sequent, SEVMS VAX, Shark, SharpOS, ShawnOS, SIBO, Sinclair, Sinix, SINTRAN III, SkyOS, Slikware, sMultiTA, SOBS, Solaris, Solar OS, Solbourne UNIX, SOS, SP6800, Spice, Spice/MT, SPIN, Spinix, SPDX, Spring, Squeak, SSP (System Support Program), STAR-OS, STARCOS, Starplex II OS, Sting, StreamOS, Subsump, SUMO, SunMOS, SunOS, SunriseOS, SuperDOS, SVM, SVR, Switch OS, Syllable, Symbian OS, SymbOS, Symobi, Symphony OS, Synapse, System 6 (Mac OS), System 7 (Mac OS), System V Release, Tabos, TABOS, TalOS, TAOS, TENEX, THE, Thix, ThreadX, ThrillOS, TI-99 4A, TinyOS, TIS APL, TNIX, TOPS-10, TOPS-20, Topsy, Tornado, Torsion, TOS, TPF (Transaction Processing Facility), TriangleOS, Tripos, TRON, TRS-DOS, Tru64 UNIX, TSX-32, TUD:OS, TUNES, TurboDOS, UberOS, UCSD-p, UDOS, Ultrix, UMDS, UMN, UNI/OS, Unicos, UNICOS/Ic, Uni FLEX, Unisys U5000, Unix System, UnixWare, Unununium, USIX, UTS, UXP/V, V2 OS, Vapour, Veloce OS3, VERSAdos, VisiOn, Visopsys, Visual Network OS, VM/ESA, VM/VSE, VME, VMS, VRTX/8002, VRTX/OS, VSE, VSOS, VSTa, VTOS, VxWorks, WEGA, WildMagnolia, Windows 7, Windows 8, Windows 10, Windows 95, Windows 98, Windows 98 SE, Windows 2000, Windows Automotive, Windows CE, Windows ME, Windows NT, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP, WinMac, WIZRD, x-kernel, XAOS, XDOS, Xenix, Xinu, xMach, XOS, XTS, Yamit, Yaxic, Yoctix, z-VM, z/OS, Z9001-OS, ZealOS, Zephyr, Zeta, Zeus Zilog, zeVenOS, ZMOS, ZotOS, and ZRTS 8000. In certain embodiments, for example, the operating system may be a Linux distribution consisting of the group selected from 3Anoppix, 64 Studio, Absolute Linux, AbulÉdu, Adamantix, ADIOS, Adler Linux, Admelix, Admiral Linux, AGNULA, Alcolix, Alinex, aLinux, AliXe, Alpine Linux, ALT Linux, amaroK Live, Amber, andLinux, Android, Android Things, Ankur, Annvix, AnNyung, Anonym.OS, ANTEMIUM, antiX, APODIO, Apricity OS, aquamorph, Arabian, ArcheOS, Archie, Arch Linux, Ark Linux, Armed Linux, ArtistX, Arudius, AsianLinux, Asianux, ASork, ASP Linux, Astaro, AsteriskNOW, Athene, ATMission, Atomix, Augustux, Aurora, Aurox, AUSTRUMI, B2D, BabelDisc, BackTrack, Baltix, Bayanihan, BearOps Linux, BeatrlX Linux, Beehive Linux, BeleniX, Bent Linux, Berry Linux, BestLinux, BIG LINUX, BinToo, BioBrew, Bioknoppix, Black Cat Linux, blackPanther, BLAG, Blin Linux, Bloody Stupid, Blue Cat Linux, BlueLinux, Bluewall, Bodhi Linux, Bonzai Linux, Bootable Cluster CD, Brillo, Buffalo, BugnuX, BU Linux, Burapha, ByzantineOS, Caixa Mágica, Caldera Linux, cAos, Carl.OS, Catix, CCux, CDlinux, Censornet, CentOS, Chakra, Chrome OS, Chromium OS, cl33n, ClarkConnect, ClearOS, cLIeNUX, Clonezilla Live, Clusterix, clusterKNOPPIX, Co-Create, CobaltOS, College, Commodore OS Vision, Condorux, Conectiva Linux, Cool Linux CD, CoreBiz, Coreboot, Corel Linux, CoreOS, Coyote, Craftworks Linux, CrunchBang, CrunchEee, CRUX, Cub Linux, Càtix, Damn Small Linux, Damn Vulnerable Linux, Danix, DARKSTAR, Debian GNU/Linux, Debris Linux, Deep-Water, Deft Linux, DeLi, Delix Linux, Dell Networking OS10, Denix, Devil, Dizinha, DLD, DNALinux, Draco Linux, Dragon Linux, Dragora, DRBL live, Dreamlinux, Dualix, Dynabolic, dyne:bolic, Dzongkha, E/OS LX Desktop, Eadem, Eagle, eAR OS, easyLinux, Easy Peasy, easys, Edubuntu, eduKnoppix, EduLinux, Ehad, Eisfair, Elbuntu, ELE, eLearnix, elementary OS, ELF, Elfstone Linux, ELinOS, Elive, ELP, ELX, Embedix, Endian, Endless OS, EnGarde, ERPOSS, ESware, Euronode, EvilEntity Linux, Evinux, EzPlanet One, FAMELIX, FaunOS, Feather, Featherweight, Fedora, Fermi, ffsearch-LiveCD, Finnix, Firefox OS, Fiubbix, Flash, FlightLinux, Flonix, Fluxbuntu, FluxFlux-Eee, Foresight, FoRK, Formilux, FoX Desktop, Freduc, free-EOS, Freedows, Freeduc, FreeNAS, Freepia, FreeSBIE, Freespire, FreevoLive, Freezy, Frugalware, FTOSX, FusionSphere, GalliumOS, GeeXboX, Gelecek, GenieOS, Gentoo, Gentoox, GEOLivre, Gibraltar, Ging, Giotto, Glendix, gNewSense, GNIX, Gnoppix, GNUbie Linux, gnuLinEx, GNUstep, GoblinX, GoboLinux, GoodGoat Linux, gOS (Google OS), GParted, Grafpup, Granular Linux, grml, Guadalinex, Guix, GuLIC-BSD, H3Knix, Haansoft, Hakin9, Halloween Linux, Hancom, Hedinux, Helix, Heretix, Hikarunix, Hiweed, Holon, HOLON Linux, Honeywall, How-Tux, Hubworx, iBox, ICE Linux, Icepack Linux, IDMS, Igelle, Igel Linux, Ignalum, Impi, Independence, IndLinux, Instant WebKiosk, IPCop, JBLinux, JeOS, Jolicloud, JoLinux, Joli OS, Julex, Jurix Linux, Juxlala, K-DEMar, K12LTSP, Kaboot, Kaella, Kaladix Linux, Kalango, Kali Linux, KANOTIX, Karamad, KateOS, Kinneret, Kiwi Linux, Klax, Klikit-Linux, K Linux, kmLinux, knoplLS, Knoppel, Knopperdisk, Knoppix, Knoppix 64, KnoppiXMAME, KnoppMyth, KnoSciences, Kodibuntu, Komodo, Kongoni, Korora, KRUD, Kubuntu, Kuki Linux, Kurumin, Kwort, L.A.S., Leetnux, Lerntux, LFS, LG3D, LibraNet Linux, LibreCMC, LIIS, Lin-X, Linare, LindowsOS, Lineox, LinEspa, LinnexOS, Linpus, Linspire, Linux+ Live, Linux-EduCD, Linux4One, Linux Antarctica, Linux by LibraNet, LinuxConsole, Linux CentOS (for example Linux CentOS 7), Linux DA OS, LinuxMCE, Linux Mint, LINUXO, LinuxOne, LinuxPPC, LinuxTLE, Linux XP, Litrix, LiveCD Router, LiveKiosk, LiVux, LLGP, LliureX, LNX-BBC, Loco, Lormalinux, I OS, LST Linux, LTSP, LUC3M, Luit, Lunar, LuteLinux, LXDEbian, Lycoris Desktop/LX, m0n0wall, Mageia, Magic, Mandrake, Mandriva, Mangaka, MAX, MaxOS, Mayix, MCNLive, Mediainlinux, Media Lab, MeeGo, MEPIS, MicroOS, MiniKazit, Minislack, Miracle, MirOS, MkLinux, Moblin, Mockup, MoLinux, Momonga, Monoppix, Monte Vista Linux, MoonOS, Morphix, MostlyLinux, MoviX, MSC, Mulimidix, muLinux, Multi Distro, Muriqui, MURIX, Musix, Mutagenix, MX Linux, Myah OS, myLinux, Nasgaia, Natures, Navyn OS, NepaLinux, NetMAX DeskTOP, NetSecL, Netstation Linux, Netwosix, Nexenta, Niigata, NimbleX, Nitix, NoMad Linux, Nonux, Nova, NST, nUbuntu, Nuclinux, NuxOne, O-Net, OcNOS, Ocularis, Ola Dom, Omega, Omoikane, Onebase Linux, OpenArtist, OpenLab, OpenLinux, OpenLX, OpenMamba, OpenMediaVault, OpenNA, Open ProgeX, Openwall, Operator, Oracle Linux, Oralux, Overclockix, P!tux, PAIPIX, paldo, Parabola, ParallelKnoppix, Pardus, Parsix, Parsix GNU/Linux, PC/OS, PCLinuxOS, Peanut Linux, PelicanHPC, Penguin Sleuth, Pentoo, Peppermint, Pequelin, pfSense, Phaeronix, Phantomix, Phat Linux, PHLAK, Pie Box, Pilot, Pingo, Pingwinek, Pioneer Linux, Plamo, PLD, PLoP Linux, Pocket Linux, Poseidon, POSTed, Power Desktop, Pozix Linux, pQui, Privatix, Progeny, ProteanOS, ProTech, PUD, Pulsar Linux, Puppy, Puredyne, QiLinux, Qimo, Qplus, Quantian, Qubes OS, Raidiator, Raspbian, Red Flag, Red Hat, Red Hat Enterprise Linux (for example Red Hat Enterprise Linux version 7), RedHawk Linux, Redmond Linux, redWall Firewall, Remix OS, Repairlix, RIoT, RIP, ROCK, Rock Linux, Rocks Cluster, ROOT, ROSA, ROSLIMS, rPath, RR4 Linux, RTLinux, Rubix, Sabayon, Sabily, Sailfish OS, Salgix, Salix OS, Salvare, SAM, Samhain Linux, Santa Fe, Sauver, SaxenOS, SCI.Linux, Scientific Linux, SCO Linux, ScrudgeWare, Securepoint, Security-Enhanced Linux (“SELinux”), Sentry Firewall, Shift Linux, Shinux, SimplyMEPIS, Skolelinux, Slack/390, Slackintosh, Slackware, Slamd64, SLAMPP, slax, SliTaz GNU/Linux, SLS, SLYNUX, SME Server, SmoothWall, SnapGear Embedded Linux, SNAPPIX, Snøfrix, SoL (Server optimized Linux), SONiC, Sorcerer, SOT Linux, Source Mage, Spectra Linux, SphinxOS, Splack, Splashtop, SprezzOS, Stampede, StartCom, STD, Stormix, StreamBOX, StressLinux, STUX, STX, Subgraph OS, Sugar On A Stick, SuliX, Sun Linux, Sun Wah, SuperGamer, SuSE, Symphony OS, System Rescue, T2, TA-Linux, Tablix, Tails (The Amnesic Incognito Live System), Tao Live, Taprobane, TechLinux, Thinstation, Tilix, Tinfoil Hat Linux, Tiny Core Linux, Titan LEV, Tizen, tomsrtbt, Tomukas, Toophpix, Topologilinux, Toutou, Trinity, Trisquel GNU/Linux, Trixbox, Troppix, Trustix, Trustverse, Truva, TumiX, TupiServer, Tuquito, Turbolinux, Turkix, Ubuntu, UbuntuME, Ubuntu Netbook Remix, Ubuntu Privacy Remix, uClinux, Ufficio Zero, UHU-Linux, uL, Ulteo, Ultima, Underground, Unifix Linux, uOS, Urli OS, UserLinux, UTILEX, Ututo, Ututo XS, Vector, Vidalinux, VideoLinux, Vine, VLOS, VNLinux, Voltalinux, Volumio, WarLinux, Wazobia, Webfish Linux, WHAX, White Box, Whitix, WIENUX, Wind River Linux, WinLinux 2001, WinSlack, Wolvix, WOMP!, X-evian, X/OS, Xandros, Xarnoppix, Xenoppix, Xfld, Ximian Desktop, xPud, Xteam, XtreemOS, Xubuntu, Yellow Dog, YES, Yggdrasil Linux, Ylmf OS, Yoper, YunOS, Zebuntu, Zentyal, Zenwalk, Zeroshell, ZoneCD, and Zorin OS.

In certain embodiments, for example, the operating system may be configured to enforce access control policies. In certain embodiments, for example, the access control policies may restrict execution of computer programs (for example user-initiated processes, boot up processes, application programs and/or operating system programs) to a predetermined (for example preconfigured) list. In certain embodiments, for example, the access control policies may restrict access to files and network resources to a predetermined (for example preconfigured) list. In certain embodiments, for example, the access control policies may be mandatory. In certain embodiments, for example, configuration of the access control policies may be non-discretionary. In certain embodiments, for example, the operating system may not provide for a root user or a superuser. In certain embodiments, for example, the operating system may be SELinux (or SE Linux or Linux SE). In certain embodiments, for example, the operating system may comprise a kernel security module, for example the operating system may be a Linux operating system and the security module may be AppArmor.

In certain embodiments, for example, memory defined by the computer-readable media may comprise a kernel space memory and a user (or application) space memory. In certain embodiments, for example, the kernel space memory may comprise kernel RAM. In certain embodiments, for example, the kernel space memory may be reserved for executing the kernel. In certain embodiments, for example, the user space memory may be reserved for executing all non-kernel user processes (for example application programs) and program modules. In certain embodiments, for example, the user space memory may comprise a portion of RAM.

In certain embodiments, for example, the one or plural nodes may comprise a network stack (also termed a “protocol stack”). In certain embodiments, for example, at least a portion of the network stack may form part of the operating system or part of the kernel of the node, processor, or computing device. In certain embodiments, for example, the network stack may comprise one or more layers according to the OSI model. In certain embodiments, for example, the network stack may comprise a physical layer consisting of hardware (for example an Ethernet interface) used to form a data connection. In certain embodiments, for example, the network stack may comprise a data link layer configured to provide data transfer to and from a remote node of the plural nodes. In certain embodiments, for example, the network stack may comprise a network layer configured to transferring variable length data sequences (called datagrams) to and from a remote node of the plural nodes. In certain embodiments, for example, the network stack may comprise a transport layer configured to transfer datagrams from a source to a destination host according to a specified protocol. In certain embodiments, for example, the specified protocol may be Transmission Control Protocol (TCP). In certain embodiments, for example, the specified protocol may be User Datagram Protocol (UDP). In certain embodiments, for example, the network stack may comprise a session layer configured to establish, manage and terminate a connection between an application executing on the node and an application executing on another node of the plural nodes. In certain embodiments, for example, the network stack may comprise a presentation layer configured to map syntax and semantics between applications communicating via the network stack. In certain embodiments, for example, the network stack may comprise an application layer configured to provide a standardized communication interface to an application executing on the node, for example an network application programming interface whereby a user process (for example a self-contained user-application program) in user space may utilize portions of the network stack.

In certain embodiments, for example, the one more of the plural nodes may comprise software. In certain embodiments, for example, the software may be an application program. In certain embodiments, for example, the software may be an end-user application program (for example a program invoked by an end-user such as a non-administrator or non-root user). In certain embodiments, for example, an application executing in an application space of a node may be identified using a user-application identifier, user-application identifier comprising an application identifier (for example a process command) and a user (for example a process owner) of the application. In certain embodiments, for example, the software may be a program not invoked by an operating system, or a program that is not an operating system program. In certain embodiments, for example, the software may be a self-contained executable configured to execute in an application space of a node of the each of one more of the plural nodes. In certain embodiments, for example, the software may be a user mode program. In certain embodiments, for example, the software may be a server. In certain applications, for example, the software may be a client. In certain embodiments, for example, the software may be a publisher. In certain applications, for example, the software may be a subscriber. In certain embodiments, for example, the software may be a publisher and/or a subscriber. In certain embodiments, for example, the software may comprise a component of a Supervisory Control and Data Acquisition (SCADA) system. In certain embodiments, for example, the software may be configured to transmit data (for example sensor data, confidential data, and/or secret data). In certain embodiments, for example, the software may be configured to receive, transmit, create, handle, manipulate, and/or store data. In certain embodiments, for example, the software may be configured to receive, transmit, create, handle, manipulate, and/or store sensitive data (for example confidential data and/or secret data). In certain embodiments, for example, the software may be configured to receive, transmit, create, handle, manipulate, and/or store sensor data. In certain embodiments, for example, the software may be updated (for example updated one time, updated plural times, or periodically updated), for example updated from a remote computer over the network. In certain embodiments, combinations of an identifier for the software and an identifier for an authorized user may be present in a preconfigured list present on the node, processor, or computing device. In certain embodiments, for example, the preconfigured list may further comprise one or plural exclusive allowed network port numbers (and optionally allowed network interface controllers) which may be associated with the software. In certain embodiments, for example, the preconfigured list may further comprise one or plural exclusive allowed network port numbers (and optionally allowed network interface controllers) to which the software may transmit or from which the software may receive data. In certain embodiments, for example, the preconfigured list may further comprise a data type or data protocol descriptor authorized for transmission or receipt by the software. In certain embodiments, for example, the preconfigured list may further comprise one or plural tunnel port numbers for a network security program adapted to communicate with the software. In certain embodiments, for example, the preconfigured list may comprise a private key (or a cryptographic parameter or primitive) configured for establishment of an encrypted network tunnel having a port of the network security program as an endpoint, the port referencing one of the one or plural tunnel port numbers (for example a private key used for cryptographic key exchange). In certain embodiments, for example, the software may be non-secure. In certain embodiments, for example, the software may not be password protected. In certain embodiments, for example, the software may be configured for packet data communication with a remote application present on a remote node but not configured for secure communication (for example not configured for secure communication of packet data by an encrypted communication protocol such as TLS).

In certain embodiments, for example, the software may comprise network security software. In certain embodiments, for example, the network security software may comprise middleware (or the software may comprise middleware which comprises the network security software) configured to execute between an application software and at least a portion of the network (for example all of the network). In certain embodiments, for example, the network security software may be resident on a common node with the application software. In certain embodiments, for example, the network security software may communicate (for example by an encrypted network tunnel between a node on which the network security software is resident and a remote node) with remote network security software present on a remote node, processor, or computing device. In certain further embodiments, for example, the remote network security software may be middleware interposed between a remote application software on the remote node and the network. In certain embodiments, for example, the network security software may be present on a first node of the plural nodes and the application software may be present on a second node of the plural nodes. In certain embodiments, for example, the first node may be a network security broker. In certain embodiments, for example, the first node may be a controller for a software-defined perimeter. In certain embodiments, for example, the first node may be a controller for a black cloud. In certain embodiments, for example, the network security software may be exclusively invoked by a root user. In certain embodiments, for example, the network security software may be first invoked by a kernel. In certain embodiments, for example, at least a portion (for example all) of the network security software may be executed with kernel priority. In certain embodiments, for example, a portion of the network security software may comprise one or plural modules executing in an application space with less than kernel priority. In certain embodiments, for example, at least one of the one or plural modules may be invoked from a shim in a network stack. In certain embodiments, execution of the network security software may comprise a single execution thread. In certain embodiments, for example, execution of the network security software may be distributed. In certain embodiments, for example, execution of the network security software may comprise plural execution threads. In certain embodiments, for example, execution of the network security software may comprise two threads, three threads, or four threads. In certain embodiments, for example, execution of the network security software may comprise at least two execution threads, for example at least three execution threads, at least four execution threads, or execution of the network security software may comprise at least ten execution threads. In certain embodiments, for example, execution of the network security software may comprise less than twenty execution threads, less than ten execution threads, less than eight execution threads, less than four execution threads, or execution of the network security software may comprise less than three execution threads. In certain embodiments, for example a first execution thread of the network security software may communicate data to and/or receive data from a second execution thread of the network security software.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a camera. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a network camera. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a networked camera. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a camera.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a video encoder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a video encoder.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a network video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a networked video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a video recorder.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an edge storage device for a video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an edge storage device for a network video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an edge storage device for a networked video recorder. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an edge storage device for a video recorder.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an audio system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an audio system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an input/output accessory of an audio system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an input/output accessory or module of an audio system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a system device, for example a network system device or a networked system device. In certain embodiments, for example, the system device may be a surveillance device. In certain embodiments, for example, the system device may be a radar-based detector.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a system device (for example on a radar-based detector or a surveillance device). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with video management software. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with surveillance software.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with security analytics. In certain embodiments, for example, the security analytics may comprise people counter software, queue monitor software, store data software, occupancy estimating software, demographic identification software, tailgate detection software, direction detection software, perimeter security software, motion detection and/or monitoring software, cross like detection software, digital autotracking software, or a combination of two or more of the foregoing.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an access control device. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an access control device. In certain embodiments, for example, the access control device of one or more of the foregoing embodiments may comprise a network door controller, a network door station, a card reader, a network I/O relay module, or a combination of two or more of the foregoing.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with or within a communications kit (for example an executive communications kit). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor in a communications kit (for example an executive communications kit).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with or within a cellular base station (for example a portable and/or deployable cellular base station). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor in a cellular base station (for example a portable and/or deployable cellular base station).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a combined router and cellular gateway. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with or within a combined router and cellular gateway. In certain embodiments, for example, the router and/or cellular gateway of one or more of the foregoing embodiments may be deployable. In certain embodiments, for example, the router and/or cellular gateway of one or more of the foregoing embodiments may be for use in a rail transportation system. In certain embodiments, for example, the router and/or cellular gateway of one or more of the foregoing embodiments may be mounted in a bulkhead of a rail car.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with or within a flyaway communications system (for example a deployable flyaway communications system). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor in a flyaway communications system (for example a deployable flyaway communications system).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an IP recorder (for example a network IP recorder or a networked IP recorder). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an IP recorder.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a hybrid network video recorder (for example a network hybrid network video recorder or a networked hybrid network video recorder). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a hybrid network video recorder.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a camera. In certain embodiments, for example, the camera may be networked. In certain embodiments, for example, the camera may be a network camera. In certain embodiments, for example, the camera may be a pan-tilt-zoom camera. In certain embodiments, for example, the camera may be a dome camera. In certain embodiments, for example, the camera may be a 360 degree camera. In certain embodiments, for example, the camera may be a bullet and box camera. In certain embodiments, for example, the camera may be a mobile camera. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a camera.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an aircraft control system, an aircraft navigation system, an air data system, an automatic direction finding system, or two or more of the foregoing systems. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an avionics system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a flight management system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an airport baggage control system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of pipeline system (for example a pipeline command and control system). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a mixed reality system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an identity management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an image generation system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a geopositioning system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an express check-in system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an integrated targeting system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a helmet mounted system (for example a helmet mounted display system). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a satellite communications transceiver. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an offsite check-in system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a service kiosk. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a software-defined radio. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an in-flight television system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a cabin management system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a video door station.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an automotive infotainment system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a telemedicine system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a cardiohealth station. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a medical imaging system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a building automation system (for example at a building automation hub).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an identity management device. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an identity management device (for example a credentialing, permissioning, and/or provisioning device). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an identity authentication device (for example a credentialing, permissioning, and/or provisioning device). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an identity authentication device (for example a credentialing, permissioning, and/or provisioning device). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an identity authorization device (for example a credentialing, permissioning, and/or provisioning device).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an access control device (for example a logical or physical access control device). In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on an access control device (for example a logical or physical access control device).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a SCADA device. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a logic processor. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a SCADA device. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a logic processor.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor used to operate and/or control digital signage.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a home energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a standalone energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an industrial energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a commercial energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a power plant energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a solar energy management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a photovoltaic energy management system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a thermostat. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an alarm system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a smoke alarm. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a carbon monoxide alarm system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a remote keyless entry system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by an embedded processor on a remote keyless entry system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications. In certain embodiments, for example, the communications may be banking communications. In certain embodiments, for example, the communications may be global payments communications. In certain embodiments, for example, the communications may be financial crime compliance communications. In certain embodiments, for example, the communications may be custodian communications. In certain embodiments, for example, the communications may be fund distribution communications. In certain embodiments, for example, the communications may be transfer agent communications. In certain embodiments, for example, the communications may be supply chain finance communications. In certain embodiments, for example, the communications may be mandate management communications. In certain embodiments, for example, the communications may be securities market communications. In certain embodiments, for example, the communications may be Treasury market communications. In certain embodiments, for example, the communications may be payment market communications. In certain embodiments, for example, the communications may be investment manager communications. In certain embodiments, for example, the communications may be Fed wire communications. In certain embodiments, for example, the communications may be investment client communications. In certain embodiments, for example, the communications may be client reporting communications. In certain embodiments, for example, the communications may be financial reporting communications.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage cable TV communications.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an elevator control system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an elevator management system. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of an elevator reporting system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a voting machine. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor, the processor in Ethernet communication with a voting machine. In certain embodiments, for example, the voting machine may be at least 10 years old. In certain embodiments, for example, the voting machine may run a Windows XP or a Windows 2000 operating system. In certain embodiments, for example, the network security software may be installed relative to a voting machine to satisfy the requirements of at least part of a state and/or federal certification (for example an Election Assistance Commission certification) process and/or testing program. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor of a voter registration database.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by critical infrastructure, for example critical infrastructure of a city, county, and/or nation.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a water management and/or control facility (for example a water supply management and/or control facility).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a waste management and/or control facility (for example a hazardous waste management and/or control facility).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications for a law enforcement activity. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a law enforcement database. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a city, county, state, or federal government function.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an educational facility. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an educational facility. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an information repository (for example a library).

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a utility. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a power generation facility. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a nuclear plant. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a hydroelectric plant.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a virtual power plant. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an energy arbitrage platform. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a smart grid.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a smart home. In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a building automation device. In certain further embodiments, for example, the building automation device may comprise a temperature management system, ventilation system, air conditioning system, security system, perimeter security system, home appliance, or a combination of two or more of the foregoing.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communication pathways in a building, the communication pathways configured according to X10, Ethernet, RS-485, 6LoWPAN, Bluetooth LE (BLE), ZigBee, Z-Wave, or two or more of the foregoing protocol.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage packet-based communications with or within an automobile.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with a perimeter security system.

In certain embodiments, for example, the network security software may be embodied in one or more non-transitory computer-readable media for execution by a processor provisioned to manage communications with an access control component of a security system (for example a perimeter security system). In certain embodiments, for example, the access control component may be a surveillance appliance. In certain embodiments, for example, the access control component may be a video camera. In certain embodiments, for example, the access control component may be an alarm. In certain embodiments, for example, the access control component may be a notification system.

In certain embodiments, for example, the authorized communication may comprise transmission of data. During at least a portion of the transmission, for example, the data or a portion thereof may be present in a data packet. Unless further specified, the term “data packet” may refer to a packaged unit of data, wherein the particular packaging may vary depending on the location of the unit of data during its transmission. Transmission of a data packet may refer to end-to-end (for example application-to-application) communication of data by one or more port-to-port connections through one or plural network stacks and optionally over a network, wherein the data packet may include a variety of protocol headers at different stages of the transmission. In certain embodiments, for example, the term “data packet” may refer to a network packet present in the network and the network packet may comprise a frame, a network protocol header (for example an IP header), a transport layer header (for example a TCP or UDP header), and a payload. In certain embodiments, for example, the term “data packet” may refer to a unit of data present in a transport layer of the network stack, the data packet comprising a transport layer header and a payload, but exclusive of a frame header and a network protocol header. In certain embodiments, for example, the data packet may comprise a unit of data ready for consumption by an application, the data packet exclusive of a transport layer header.

In certain embodiments, for example, authorized communication may comprise communication between an application program on a first node of the plural nodes and an application program on a second node of the plural nodes. In certain embodiments, for example, the first node and the second node may be different nodes. In certain embodiments, for example, the first node and the second node may be the same node, processor, or computing device. In certain embodiments, for example, the first node and the second node may be virtual nodes (for example the first node may be a first virtual node on a machine and the second node may be a second virtual node on the machine or a different machine).

In certain embodiments, for example, authorized communication may comprise communication between a first application and a second application wherein the communication passes through one or plural network security software. In certain embodiments, for example, the software may be a middleware. In certain embodiments, for example, the authorized communication may pass through one network security software. In certain embodiments, for example, the authorized communication may pass through plural network security software (for example, two network security software, three network security software, or four network security software), wherein at least two (for example two, or for example each) of the plural network security software are cooperatively configured to authorize the authorized communication. In certain embodiments, for example, a first network security software may be execute in a kernel of a node and a second network security software may execute in a virtual machine on the node, processor, or computing device.

In certain embodiments, for example, at least one of the one or plural network security software may be middleware positioned between the first application and the second application. In certain embodiments, for example, the authorized communication may comprise a first communication from the first application to first network security software on the first node, a second communication from the first network security software to second network security software on the second node, and a third communication from the second network security software to the second application.

In certain embodiments, for example, the first communication may comprise communication from a port of the first application program to a port of the first network security software by a loopback interface in a network stack of the first node, processor, or computing device. In certain embodiments, for example, the first communication may comprise communication from the first application to the first network security software by a procedure call. In certain embodiments, for example, the first communication may comprise a kernel function call (for example a kernel read and/or a kernel write call). In certain embodiments, for example, the second communication may comprise communication over a network tunnel having a port of the first network security software and a port of the second network security software as endpoints. In certain embodiments, for example, at least a portion of the second communication may be encrypted. In certain embodiments, for example, a metadata portion of the second communication may be encrypted. In certain embodiments, for example, the metadata portion may be encrypted by the first network security software and decrypted by the second network security software. In certain embodiments, for example, the payload portion of the communication may be encrypted. In certain embodiments, for example, the payload portion may be encrypted by the first network security software and decrypted by the second network security software. In certain embodiments, for example, contiguous metadata and payload data may be encrypted to form a contiguous segment of encrypted information. In certain embodiments, for example, the contiguous segment may be encrypted by the first network security software and decrypted by the second network security software. In certain embodiments, for example, a metadata portion of the communication may be encrypted by the first network security software and decrypted by the second network security software while a payload portion of the communication may be encrypted by a third software present on the first node and decrypted by a fourth software present on the second node, processor, or computing device. In certain embodiments, for example, the third software may be the first application and/or the fourth software may be the second application. In certain embodiments, for example, the third software may be a security layer software present on the first node (for example SSL, TLS or IPsec software) and/or the fourth software may be a security layer software present on the second application. In certain embodiments, for example, the third communication may comprise communication from a port of the second network security software to a port of the second application program by a loopback interface of the second node, processor, or computing device. In certain embodiments, for example, the first communication may comprise communication from the second network security software to the second application program by a procedure call. In certain embodiments, for example, the second communication may be transparent to the first application and the second application. In certain embodiments, for example, the first application and the second application may not be aware of the second communication. In certain embodiments, for example, the first communication may be unencrypted. In certain embodiments, for example, the second communication may be unencrypted. In certain embodiments, for example, the first communication and/or the second communication may be unencrypted. In certain embodiments, for example, the first communication may be encrypted. In certain embodiments, for example, the second communication may be encrypted. In certain embodiments, for example, the first communication and/or the second communication may be encrypted. In certain embodiments, for example, the first communication may result from an attempt by the first application to establish a direct port-to-port connection with the second application. In certain embodiments, for example, the second communication may result from an attempt by the second application to bind a port to a physical interface of the second node, processor, or computing device. In certain embodiments, for example, the second communication may result from an attempt by the second application to establish a listening port (for example a listening port bound to a physical interface) on the second node, processor, or computing device. In certain embodiments, for example, the authorized communication may comprise communication to or from one or more ports having a pre-selected port number. In certain embodiments, for example, the authorized communication may comprise communication to or from one or more ephemeral ports. In certain embodiments, for example, port endpoints for the first communication may be ephemeral. In certain embodiments, for example, a source port for the second communication may be ephemeral and destination port for the second communication may be pre-selected (for example a fixed port number specified to network security software responsible for establishing the second connection). In certain embodiments, for example, a source port of the third communication may be ephemeral and a destination port of the third communication may be pre-selected. In certain embodiments, for example, the source and destination ports of each of the first communication, second communication, and third communication may be pre-selected.

In certain embodiments, for example, the first connection may be a connection according to TCP protocol. In certain embodiments, for example, the first connection may be a connection according to UDP. In certain embodiments, for example, the first connection may be a connection according to a mid-weight UDP protocol.

In certain embodiments, for example, the second connection may be a connection according to TCP protocol. In certain embodiments, for example, the second connection may be a connection according to UDP protocol. In certain embodiments, for example, the second connection may be a connection according to a mid-weight UDP protocol.

In certain embodiments, for example, the third connection may be a connection according to TCP protocol. In certain embodiments, for example, the third connection may be a connection according to UDP protocol. In certain embodiments, for example, the third connection may be a connection according to a mid-weight UDP protocol.

In certain embodiments, for example, each of the first connection, the second connection, and the third connection may be a connection according to TCP protocol. In certain embodiments, for example, each of the first connection, the second connection, and the third connection may be a connection according to UDP protocol. In certain embodiments, for example, each of the first connection, the second connection, and the third connection may be a connection according to a mid-weight UDP protocol. In certain embodiments, for example, each of the first connection, the second connection, and the third connection may be according to the same connection protocol. In certain embodiments, for example, each of the first connection and the second connection may be according to the same connection protocol and the third connection may be according to a different communication protocol. In certain embodiments, for example, each of the first connection, the second connection, and the third connection may be according to different communication protocol.

In certain embodiments, for example, the authorized communication may comprise communication over an encrypted tunnel having, as endpoints, a port of the first application and a port of the second application. In certain embodiments, for example, the first application and the second application may each comprise one or plural network security modules for authorized communication between the applications. In certain embodiments, for example, the encrypted tunnel may be authorized based on communication between the first node and a third node, the third node hosting network security middleware, and further based on communication between the second node and a fourth node, the fourth node hosting network security middleware. In certain embodiments, for example, the third node and the fourth node may be the same node (wherein the respective network security middleware may be the same or different). In certain embodiments, for example, the third node and the fourth node may be different nodes. In certain embodiments, for example, the third node and the first node may be the same node while the fourth node and the second node may be different nodes. In certain embodiments, for example, the first node, third node, and fourth node may be the same node, processor, or computing device. In certain embodiments, for example, the second node, third node, and fourth node may be the same node, processor, or computing device.

In certain embodiments, for example, the authorized communication may pass through a third node hosting network security software, the third node disposed, for purposes of the communication, between the first node and the second node, processor, or computing device. In certain embodiments, for example, the authorized communication may comprise a network tunnel between the first node and the third node (for example a network tunnel such as an encrypted network tunnel having the first application (or a shim in the network stack application programming interface) and network security software present on the third node as endpoints and a different network tunnel between the third node and the second node, processor, or computing device.

In certain embodiments, for example, a first node of the plural nodes and a second node of the plural nodes may form a secure connection. In certain embodiments, for example, the secure connection may comprise a network tunnel. In certain embodiments, for example, the network tunnel may be a packet network tunnel. In certain embodiments, for example, the network tunnel may be formed according to an encrypted communication protocol, whereby each data packet transmitted through the network tunnel may be encrypted at a first endpoint of the network tunnel present on the first node, passed through the network tunnel, and then decrypted at a second endpoint of the network tunnel present on the second node, processor, or computing device. In certain embodiments, for example, the encrypted communication protocol may be implemented in the OSI transport layer. In certain further embodiments, for example, the transport layer encrypted communication protocol may be selected from the group consisting of Secure Socket Layer (SSL) protocol, Transport Layer Security (TLS), Secure Shell (SSH) protocol, and a combination of two or more of the foregoing protocols. In certain embodiments, for example, the encrypted communication protocol may be implemented in the OSI network layer or data link layer. In certain further embodiments, for example, the encrypted communication protocol may be selected from the group consisting of IPsec, Layer 2 Tunneling Protocol (L2TP) over IPsec, or Ethernet over IPsec.

In certain embodiments, for example, encryption and decryption may use an encryption key wherein the key is established by executing a key exchange algorithm between software executing on the first node and software executing on the second node, processor, or computing device. In certain embodiments, for example, the key exchange algorithm may be selected from the group consisting of Rivest, Shamir, Adleman (RSA), Diffie-Hellman (DH), Diffie-Hellman Ephemeral (DHE), Elliptic-Curve Diffie-Hellman (ECDH), Kerberos (KRB5), Secure Remote Password Protocol (SRP), Pre-shared key (PSK), Digital Signature Algorithm (DSA), Elliptic Curve Digital Signature Algorithm (ECDSA), and Digital Signature Standard (DSS).

In certain embodiments, for example, the encryption and decryption may be performed using a symmetric encryption algorithm. In certain embodiments, for example, the symmetric encryption algorithm may be selected from the group consisting of Triple Data Encryption Algorithm (3DES), Advanced Encryption Standard (AES), Camelia (Block cipher developed by Mitsubishi and NTT), Data Encryption Standard (DES), Fortezza (Security token based cipher), GOST (Block cipher developed in USSR), International Data Encryption Algorithm (IDEA), Rivest Cipher 2 (RC2), Rivest Cipher 4 (RC4), and SEED (Block cipher developed by Korean Information Security Agency).

In certain embodiments, for example, each data packet passed through the network tunnel may contain a message authentication code, comprising a hashed value for a portion of the data packet. In certain embodiments, for example, the hashed value may be obtained by passing the portion of the data packet through a hashing algorithm. In certain embodiments, for example, the hashing algorithm may be selected from the group consisting of BLAKE-256, BLAKE-512, BLAKE2s, BLAKE2b, Elliptic Curve Only Hash (ECOH), the Fast Syndrome-based (FSB) hash, GOST, Grøstl, HAS-160, HAVAL, JH, the Message Digent-2 (MD2) algorithm, MD4, MD5, MD6, RadioGatún, the RACE Integrity Primitives Evaluation Message Digest (RIPEMD), RIPEMD-128, RIPEMD-160, RIPEMD-320, the Secure Hash Algorithm-1 (SHA-1), SHA-2, SHA-224, SHA-256, SHA-384, SHA-512, SHA-3, Skein, Snefru, Spectral Hash, Streebog, SWIFFT, Tiger, Whirlpool-0, Whirlpool-T, and Whirlpool.

In certain embodiments, for example, authorized communication may comprise transmission of metadata-containing data packets over a network tunnel. In certain embodiments, for example, the metadata-containing packets may conform to Internet Protocol version 4 (IPv4). In certain embodiments, for example, the metadata-containing packets may conform to Internet Protocol version 6 (IPv6). In certain embodiments, for example, the metadata may be positioned at a predetermined location (for example start at a predetermined location) in a data packet. In certain embodiments, for example, the metadata may be positioned after (for example immediately after, after a predetermined buffer, or at a predetermined offset from) a transport layer header of the data packet. In certain embodiments, for example, the metadata may be positioned between the transport layer header and payload data of the network packet.

In certain embodiments, for example, the metadata may be encrypted according to an encryption scheme of the network tunnel (for example one of the encryption schemes described herein). In certain embodiments, for example, the metadata may be encrypted with data packet payload data to form single ciphertext. In certain embodiments, for example, the metadata be encrypted separately from data packet payload data (or the metadata may be encrypted and payload data may not be encrypted). In certain embodiments, for example, the metadata be encrypted by a first network security software and data packet payload data may be encrypted by a second network security software.

In certain embodiments, for example, the metadata may be built and inserted into a data packet by a first network security software present on a first node of the plural nodes. In certain embodiments, for example, the first node may coincide with a source node (or node-of-origin) for the data packet (for example the first node may be a node containing first application software transmitting data contained in a payload of the data packet such as from program memory of the first application software). In certain embodiments, for example, the first node may be a waypoint node (or intermediate node) disposed between a source node for the data packet and a final destination node for the data packet. In certain embodiments, for example, the first node may be directly connected by an Ethernet connection to a source node for the data packet. In certain embodiments, for example, the second node may be directly connected by an Ethernet connection to a final destination node for the data packet.

In certain embodiments, for example, the metadata may be encrypted by software present in an encryption layer (for example TLS, SSL, or IPsec). In certain embodiments, for example, the metadata may be encrypted by an encryption module, subroutine, function, or the like. In certain embodiments, for example, the metadata may be encrypted using a single-use cryptographic key (for example an ECDH-derived key which is rotated with each packet transmission through the network tunnel), whereby the same metadata would appear different in different data packets due to use of a different cryptographic key in each instance. In certain embodiments, for example, the first network security software may comprise the encryption layer software. In certain embodiments, for example, the first network security software may invoke (for example call) the encryption layer software. In certain embodiments, for example, the first network security software may invoke the encryption module, subroutine, or function. In certain embodiments, for example, the encryption layer software or encryption module may be present in an OSI application layer of the first node, processor, or computing device. In certain embodiments, for example, the encryption layer software or encryption module may be present in a kernel layer (for example a kernel portion of a network stack) of the first node, processor, or computing device.

In certain embodiments, for example, the metadata may be extracted and parsed from a data packet by a second network security software present on a second node of the plural nodes. In certain embodiments, for example, the second node may coincide with a final destination node for the data packet (for example a final destination node comprising a second application configured to receive payload data present in the data packet such as in program memory of the second application). In certain embodiments, for example, the second node may be a waypoint node (or intermediate node) disposed between a source node for the data packet and a final destination node for the data packet. In certain embodiments, for example, the second node may be directly connected by an Ethernet connection to the source node for the data packet. In certain embodiments, for example, the second node may be directly connected by an Ethernet connection to the final destination node for the data packet.

In certain embodiments, for example, the metadata extracted from the data packet may be encrypted (as discussed herein). In certain embodiments, for example, the metadata may be decrypted by encryption layer software (for example TLS, SSL, or IPsec). In certain embodiments, for example, the metadata may be decrypted by an encryption module, subroutine, function, or the like (collectively referred to as “module” for purposes herein). In certain embodiments, for example, the decrypting may be performed prior to the parsing. In certain embodiments, for example, the decrypting may be performed subsequent to the parsing. In certain embodiments, for example, the second network security software may comprise the encryption layer software. In certain embodiments, for example, the second network security software may invoke (for example call) the encryption layer software. In certain embodiments, for example, the second network security software may invoke the encryption module. In certain embodiments, for example, the encryption layer software or encryption module may be present in an OSI application layer of the second node, processor, or computing device. In certain embodiments, for example, the encryption layer software or encryption module may be present in a kernel layer (for example a kernel portion of a network stack) of the second node, processor, or computing device.

In certain embodiments, for example, the metadata may comprise one or plural parameters. In certain embodiments, for example, the one or plural parameters may comprise a packet type identification code. In certain embodiments, for example, the packet type identification code may be interpreted by network security software to indicate the data packet is configured to be used for negotiation (for example authentication and/or authorization) of a network tunnel. In certain embodiments, for example, the packet type identification code may be interpreted by network security software to indicate the data packet is configured to be transmitted through an existing network tunnel (for example an authenticated and/or authorized network tunnel). In certain embodiments, for example, the packet type identification code may be interpreted by network security software to indicate the data packet contains application payload data. In certain embodiments, for example, the packet type identification code may be interpreted by network security software to determine a connection state for a network tunnel. In certain embodiments, for example, the packet type identification code may be positioned at a predetermined location (for example start at a predetermined location) in the data packet. In certain embodiments, for example, the packet type identification code may be positioned after (for example immediately after, after a predetermined buffer, or at a predetermined offset from) a transport layer header of the data packet. In certain embodiments, for example, the packet type identification code may occupy a predetermined location of the metadata. In certain embodiments, for example, the packet type identification code may be positioned at one end (for example at the beginning or the end closest to a transport layer header of the data packet) of the metadata. In certain embodiments, for example, the packet type identification code (prior to encryption) may be an integer in the range of 0-2³² (i.e., 0-4,294,967,295).

In certain embodiments, for example, the one or plural parameters may comprise one or plural node descriptors. In certain embodiments, for example, the one or plural parameters may be a node descriptor for a source node of the data packet. In certain embodiments, for example, the one or plural parameters may be a node descriptor for a source node of payload data (for example payload data that will be transmitted in a subsequent data packet by an application resident on the source node identified by the node descriptor). In certain embodiments, for example, the one or plural parameters may be a node descriptor for a destination node of payload data (for example payload data that will be transmitted in a subsequent data packet to an application resident on the destination node identified by the node descriptor). In certain embodiments, for example, the one or plural node descriptors may be nonpublic. In certain embodiments, for example, the one or plural node descriptors may be a shared secret among at least two of the plural nodes. In certain embodiments, for example, the one or plural node descriptors may be a shared secret among less than all of the plural nodes. In certain embodiments, for example, the one or plural node descriptors may have a size of at least 64 bits, for example at least 128 bits, at least 256 bits, at least 512 bits, at least 1024 bits, at least 2048 bits, at least 4096 bits, at least 8192 bits, at least 16384 bits, at least 32768 bits, or the one or plural node descriptors may have a size of at least 65536 bits. In certain embodiments, for example, the one or plural node descriptors may have a size of 64 bits, 128 bits, 256 bits, 512 bits, 1024 bits, 2048 bits, 4096 bits, 8192 bits, 16384 bits, 32768 bits, or the one or plural node descriptors may have a size of 65536 bits. In certain embodiments, for example, the one or plural node descriptors may have a size of less than 8192 bits, for example less than 4096 bits, less than 2048 bits, less than 1024 bits, or the one or plural node descriptors may have a size of less than 256 bits. In certain embodiments, for example, a portion of the one or plural node descriptors may comprise a company identifier. In certain embodiments, for example, a portion of the one or plural node descriptors may comprise a device-type identifier. In certain embodiments for example, a portion of the one or plural node descriptors may comprise a random number produced by a random number generator. In certain embodiments, for example, the random number may comprise at least 90% of the bits of the one or plural node descriptors, for example at least 95%, at least 96%, at least 97%, at least 98%, at least 98.5%, at least 99%, at least 99.5%, at least 99.9% or the random number may comprise at least 99.9% of the bits of the one or plural node descriptors. In certain embodiments, for example, the random number may comprise less than 99% of the bits of the one or plural node descriptors, for example less than 98%, or the random number may comprise less than 95% of the bits of the one or plural node descriptors. In certain embodiments, for example, the random number may comprise in the range of 95-99.9% of the bits of the one or plural node descriptors, for example in the range of 98-99% of the bits of the one or plural node descriptors. In certain embodiments, for example, the sum of digits of the one or plural node descriptors may be a prime number. In certain embodiments, for example, the one or plural node descriptors may accompany an application data payload in the data packet. In certain embodiments, for example, the one or plural node descriptors may be present in a data packet that does not contain an application data payload (for example a data packet used for negotiation of a network tunnel prior to the transmission of application data). In certain embodiments, for example, the metadata may comprise a packet type identification code and the one or plural node descriptors. In certain embodiments, for example, the one or plural node descriptors may be positioned at a predetermined location (for example start at a predetermined location) in the data packet. In certain embodiments, for example, the one or plural node descriptors may be positioned after (for example immediately after, after a predetermined buffer, or at a predetermined offset from) a transport layer header of the data packet. In certain embodiments, for example, the one or plural node descriptors may occupy a predetermined location of the metadata. In certain embodiments, for example, the one or plural node descriptors may be positioned after a packet type identification code at one end (for example at the beginning or the end closest to a transport layer header of the data packet) of the metadata.

In certain embodiments, for example, the one or plural parameters may comprise one or plural parameters for payload data. In certain embodiments, for example, the one or plural payload data parameters may comprise an application identification code. In certain embodiments, for example, the application identification code may have a length of at least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the application identification code may have a length of no more than 64 bits, for example no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the application identification code may have a length in the range of 8-64 bits, for example in the range of 8-32 bits, or in the range of 8-16 bits. In certain embodiments, for example, the one or plural payload data parameters may comprise an application user identification code. In certain embodiments, for example, the application user identification code may have a length of at least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the application user identification code may have a length of no more than 64 bits, for example no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the application user identification code may have a length in the range of 8-64 bits, for example in the range of 8-32 bits, or in the range of 8-16 bits. In certain embodiments, for example, the application identification code may be shorter than the application user identification code. In certain embodiments, for example, the application user identification code may be at least twice as long as the application identification code. In certain embodiments, for example, the one or plural payload data parameters may comprise an application identification code for a source application for the payload data. In certain embodiments, for example, the one or plural payload data parameters may comprise an application user identification code for a user of the source application for the payload data. In certain embodiments, for example, the one or plural payload data parameters may comprise an application identification code for a destination application for the payload data. In certain embodiments, for example, the combined length of the application identification code and the application user identification code may be least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the combined length of the application identification code and the application user identification code may be no more than 128 bits, for example no more than 64 bits, no more than 48 bits, no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the combined length of the application identification code and the application user identification code may have a length in the range of 8-64 bits, for example in the range of 24-64 bits, or in the range of 36-64 bits. In certain embodiments, for example, the one or plural payload data parameters may comprise an application user identification code for a user of the destination application for the payload data. In certain embodiments, for example, the one or plural payload data parameters may comprise a data type descriptor. In certain embodiments, for example, the data type descriptor may comprise a data type protocol. In certain embodiments, for example, the data type descriptor may comprise a data topic. In certain embodiments, for example, the data type descriptor may comprise a file size (for example a total size of a file being transmitted by one or more payload data). In certain embodiments, for example, the data type descriptor may comprise a maximum file size (for example a maximum size of a file being transmitted by one or more payload data). In certain embodiments, for example, the data type descriptor may comprise a file name. In certain embodiments, for example, the data type descriptor may comprise a command type. In certain embodiments, for example, the command type may be selected from the group consisting of SQLread, SQLwrite, AND/OR, ALTER TABLE, AS (alias), BETWEEN, CREATE DATABASE, CREATE TABLE, CREATE INDEX, CREATE VIEW, DELETE, DROP DATABASE, DROP INDEX, DROP TABLE, EXISTS, GROUP BY, HAVING, IN, INSERT INTO, INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN, LIKE, ORDER BY, SELECT, SELECT *, SELECT DISTINCT, SELECT INTO, SELECT TOP, TRUNCATE TABLE, UNION, UNION ALL, UPDATE, WHERE, and a combination of two or more of the foregoing command types. In certain embodiments, for example, the data type descriptor may comprise a date/time (for example a transmission date/time or a deadline). In certain embodiments, for example, the data type descriptor may comprise a time-to-live of the payload data. In certain embodiments, for example, the data type descriptor may have a size of at least 64 bits, for example at least 128 bits, at least 256 bits, at least 512 bits, at least 1024 bits, at least 2048 bits, at least 4096 bits, at least 8192 bits, at least 16384 bits, at least 32768 bits, or the data type descriptor may have a size of at least 65536 bits. In certain embodiments, for example, the data type descriptor may have a size of less than 8192 bits, for example less than 4096 bits, less than 2048 bits, less than 1024 bits, or the data type descriptor may have a size of less than 256 bits.

In certain embodiments, for example, the metadata may comprise a packet type identification code and the one or plural payload data parameters. In certain embodiments, for example, the one or plural payload data parameters may be positioned in a data packet at a location where a packet type identification code would be present (for example, the data packet may contain the one or plural payload data parameters instead of the packet type identification code). In certain embodiments, for example, the one or plural payload data parameters may be positioned at a predetermined location (for example start at a predetermined location) in the data packet. In certain embodiments, for example, the one or plural payload data parameters may be positioned after (for example immediately after, after a predetermined buffer, or at a predetermined offset from) a transport layer header of the data packet. In certain embodiments, for example, the one or plural payload data parameters may occupy a predetermined location of the metadata. In certain embodiments, for example, the one or plural payload data parameters may be positioned after a packet type identification code at one end (for example at the beginning or the end closest to a transport layer header of the data packet) of the metadata.

In certain embodiments, for example, the authorized communication may comprise transmission of a network tunnel connection request packet (for example a request packet arising from a client connection request such as a request transmitted by a network security software), the request packet comprising encrypted metadata containing a packet type identification code, the packet type identification code a connection request identification code. In certain embodiments, for example, the connection request packet may conform to a protocol. In certain further embodiments, for example, the protocol may be UDP or TCP.

In certain embodiments, for example, the authorized communication may comprise transmission of a network tunnel connection request reply packet (for example a request packet from a server such as a reply from a network security software responding to a client connection request such as a request transmitted by a different network security software), the request reply packet comprising encrypted metadata containing a packet type identification code, the packet type identification code comprising a connection request reply identification code (for example a code having a different value from the connection request identification code). In certain embodiments, for example, the connection request reply packet may conform to a protocol. In certain further embodiments, for example, the protocol may be UDP or TCP.

In certain embodiments, for example, the authorized communication may comprise transmission of a node authentication and authorization packet. In certain embodiments, for example, the node authentication and authorization packet may comprise encrypted metadata containing a node validation packet type indicator and a node descriptor. In certain embodiments, for example, establishing authorized payload data communication may comprise: (a) transmitting a first node authentication and authorization packet from a first node network security software resident on a first node to second network security software present on a second node, followed by (b) transmitting a second node authentication and authorization packet from the second network security software to the first network security software.

In certain embodiments, for example, the authorized communication may comprise transmission of a payload data authorization and authentication packet. In certain embodiments, for example, the payload data authentication and authorization packet may comprise encrypted metadata containing a payload data validation packet type indicator and a payload data parameter. In certain embodiments, for example, the payload data parameter may comprise an application identification code for an application resident on a node transmitting the payload data authorization and authentication packet, an application user identification code for a user of the resident application, and a data type or data protocol for payload data to be transmitted by a network tunnel configured according to the payload data authorization and authentication packet. In certain embodiments, for example, establishing authorized payload data communication may comprise: (a) transmitting a first payload data authentication and authorization packet from a first node network security software resident on a first node to second network security software present on a second node, followed by (b) transmitting a second payload data authentication and authorization packet from the second network security software to the first network security software.

In certain embodiments, for example, authorized communication may comprise transmission of a payload data packet. In certain embodiments, for example, the payload data packet may comprise encrypted payload data authentication and authorization metadata and payload data. In certain embodiments, for example, the metadata may be exclusive of a packet type identification code.

In certain embodiments, for example, authorized communications comprising transfer of data packets across the network may comprise communications between a first node of the plural nodes and a further node (for example a second node) of the plural nodes. In certain embodiments, for example, establishment and coordination of the authorized communications may be performed by a first network security software cooperatively configured with a second network security software (for example a first network security software resident on the first node and a second network security software resident on the second node). In certain further embodiments, for example, the first network security software and the second network security software may be different copies of the computer-readable program code (for example copies obtained from different copies of the at least one component).

In certain embodiments, for example, the first network security software may have access to a first preconfigured list, for example a first preconfigured list stored in non-transitory storage media present on the same node as the first network security software, or otherwise accessible to the first network security software. In certain embodiments, for example, the second network security software may have access to a second preconfigured list, for example a second preconfigured list stored in non-transitory storage media present on the same node as the second network security software, or otherwise accessible to the second network security software. In certain embodiments, for example, the first preconfigured list and the second preconfigured list may be aligned to enable the first network security software and the second security software to cooperatively negotiate connections for authorized communications. In certain embodiments, for example, the first preconfigured list and the second preconfigured list may together exclusively define the authorized communications permitted between an application (for example a user-application) on the first node and an application (for example a user-application) on the second node, or may exclusively define the authorized port-to-port communications. In certain embodiments, for example, the first network security software may terminate any attempt by an application resident on the first node to transmit packet data to the second node, or may drop (or quarantine) any packets received at the first node sent from the second node, that are not in conformance with the first preconfigured list. Similarly, in certain embodiments, for example, the second network security software may terminate any attempt by an application resident on the second node to transmit packet data to the first node, or may drop any packets received at the second node sent from the first node, that are not in conformance with the second preconfigured list. In certain further embodiments, for example, the non-conformance may comprise failure of a portion of the destination port numbers and/or the metadata to match expected values, the expectation regarding the expected values based on parameters present in the second preconfigured list.

In certain embodiments, for example, each of the first preconfigured list and/or a further (or second) preconfigured list may comprise a series of records, each record in the form of an n-tuple. In certain embodiments, for example, the record length may be not fixed, i.e., it may vary from record to record. In certain embodiments, for example, each of the first preconfigured list and/or the second preconfigured list may be a binary file. In certain embodiments, for example, each of the first preconfigured list and/or the second preconfigured list may be encrypted. In certain embodiments, for example, each of the first preconfigured list and/or the second preconfigured list may be read-only. In certain embodiments, for example, the first preconfigured list may be read only by a single first network security software module of the first network security software having access (for example having sole access) to a first preconfigured list decryption key. In certain embodiments, for example, the first preconfigured list decryption key may be stored in a memory location (for example a volatile memory location) known only to the first network security software module. In certain embodiments, for example, the memory location may be specific, unique to, and/or set during compilation of the first network security software module (i.e., recompilation of the first network security software module would result in a different memory location). In certain embodiments, for example, the first preconfigured list decryption key may be specific to the compilation of the first network security software module. In certain embodiments, for example, the second preconfigured list may be read only by a single second network security software module of the second network security software having access (for example having sole access) to a second preconfigured list decryption key. In certain embodiments, for example, the second preconfigured list decryption key may be stored in a memory location (for example a volatile memory location) known only to the second network security software module. In certain embodiments, for example, the memory location may be specific, unique to, and/or set during compilation of the second network security software module (i.e., recompilation of the second network security software module would result in a different memory location). In certain embodiments, for example, the second preconfigured list decryption key may be specific, unique to, and/or set during compilation of the second network security software module.

In certain embodiments, for example, each record of the each of the first preconfigured list and a further (for example, the second) preconfigured list may be interpretable by the first network security software and the second network security software, respectively, to form an authorized connection for authorized communication. In certain embodiments, for example, the first preconfigured list may contain a first record interpretable by the first network security software and the second preconfigured list may contain a second record interpretable by the second network security software for forming an authorized connection for authorized communication between the first node and the second node, processor, or computing device.

In certain embodiments, for example, each of the first record and a further record (for example, the second record) may contain a node identifier or a node identification code for the source node (the source node may be the first node or the second node) from which packet data will be transmitted in the authorized communication. In certain embodiments, for example, each of the first record and the second record may contain a node identification code for the destination node (the destination node may be the first node or the second node different from the source node) to which packet data will be transmitted in the authorized communication. In certain embodiments, for example, the first network security software and the second network security software may each exchange with one another the node identification code that corresponds to their status (source or destination). In certain further embodiments, for example, the mutual exchange may occur over an encrypted tunnel having the first network security software and the second network security software as endpoints. In certain further embodiments, for example, the exchanged node identification codes may be validated by the receiving network security software by reference to the respective first record or second record. In certain embodiments, for example, the mutual validating may be used to partially authorize the aforementioned encrypted tunnel. In certain embodiments, for example, each of the node identification codes may have a size of at least 64 bits, for example at least 128 bits, at least 256 bits, at least 512 bits, at least 1024 bits, at least 2048 bits, at least 4096 bits, at least 8192 bits, at least 16384 bits, at least 32768 bits, or each of the node identification codes may have a size of at least 65536 bits. In certain embodiments, for example, each of the node identification codes may have a size of 64 bits, 128 bits, 256 bits, 512 bits, 1024 bits, 2048 bits, 4096 bits, 8192 bits, 16384 bits, 32768 bits, or each of the node identification codes may have a size of 65536 bits. In certain embodiments, for example, each of the node identification codes may have a size of less than 8192 bits, for example less than 4096 bits, less than 2048 bits, less than 1024 bits, or each of the node identification codes may have a size of less than 256 bits. In certain embodiments, for example, a portion of each of the node identification codes may comprise a company identifier. In certain embodiments, for example, a portion of each of the node identification codes may comprise a device-type identifier. In certain embodiments for example, a portion of each of the node identification codes may comprise a random number produced by a random number generator. In certain embodiments, for example, the random number may comprise at least 90% of the bits of each of the node identification codes, for example at least 95%, at least 96%, at least 97%, at least 98%, at least 98.5%, at least 99%, at least 99.5%, at least 99.9% or the random number may comprise at least 99.9% of the bits of each of the node identification codes. In certain embodiments, for example, the random number may comprise less than 99% of the bits of each of the node identification codes, for example less than 98%, or the random number may comprise less than 95% of the bits of each of the node identification codes. In certain embodiments, for example, the random number may comprise in the range of 95-99.9% of the bits of each of the node identification codes, for example in the range of 98-99% of the bits of each of the node identification codes. In certain embodiments, for example, the sum of digits of each of the node identification codes may be a prime number.

In certain embodiments, for example, each of the first record and the second record may contain a source universal application identifier for the source application program (corresponding to the first application or the second application) generating the packet data in an authorized communication. In certain embodiments, for example, the application identifier and the user for the application may correspond to or be based on values obtained by a process status check command. Similarly, in certain embodiments, for example, each of the first record and the second record may contain a destination universal application identifier for the destination application program (corresponding to the first application or the second application) receiving the packet data in an authorized communication. In certain embodiments, for example, the source universal application identifier may comprise an application identifier and a user for the application. In certain embodiments, for example, the first network security software and the second network security software may each exchange with one another the universal application identifier that corresponds to their status (source or destination). In certain further embodiments, for example, the mutual exchange may occur over an encrypted tunnel having the first network security software and the second network security software as endpoints. In certain further embodiments, for example, the exchanged universal application identifiers may be validated by the receiving network security software by reference to the respective first record or second record. In certain embodiments, for example, the mutual validating may be used to partially authorize the aforementioned encrypted tunnel. In certain embodiments, for example, a source universal application identifier may be included in a data packet and validated against the respective record (the first record or the second record) of the destination node in order to authenticate and authorize the data packet. In certain embodiments, for example, each of the source and destination application identifiers may have a length of at least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the application identifier may have a length of no more than 64 bits, for example no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the application identifier may have a length in the range of 8-64 bits, for example in the range of 8-32 bits, or in the range of 8-16 bits. In certain embodiments, for example, the application user may have a length of at least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the each of the source and destination application user may have a length of no more than 64 bits, for example no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the application user may have a length in the range of 8-64 bits, for example in the range of 8-32 bits, or in the range of 8-16 bits. In certain embodiments, for example, the universal application identifier may be least 8 bits, for example at least 16 bits, at least 32 bits, or at least 64 bits. In certain embodiments, for example, the each of the source and destination universal application identifier may be no more than 128 bits, for example no more than 64 bits, no more than 48 bits, no more than 32 bits, no more than 16 bits, or no more than 8 bits. In certain embodiments, for example, the universal application identifier may have a length in the range of 8-64 bits, for example in the range of 24-64 bits, or in the range of 36-64 bits.

In certain embodiments, for example, each of the first record and the second record may contain a code for a network interface controller of the source node (the source node may be the first node or the second node) from which packet data will be transmitted in the authorized communication. In certain embodiments, for example, each of the first record and the second record may contain a code for the network interface controller for the destination node (the destination node may be the first node or the second node different from the source node) to which packet data will be transmitted in the authorized communication. In certain embodiments, for example, each of the codes may be processed to obtain corresponding network addresses (for example IP addresses). In certain embodiments, for example, the corresponding network addresses may define an authorized source network address and an authorized destination network address in one or plural packet headers. In certain embodiments, for example, each of the network interface controller codes may have a size of at least 64 bits, for example at least 128 bits, at least 256 bits, at least 512 bits, at least 1024 bits, at least 2048 bits, at least 4096 bits, at least 8192 bits, at least 16384 bits, at least 32768 bits, or each of the network interface controller codes may have a size of at least 65536 bits. In certain embodiments, for example, each of the network interface controller codes may have a size of 64 bits, 128 bits, 256 bits, 512 bits, 1024 bits, 2048 bits, 4096 bits, 8192 bits, 16384 bits, 32768 bits, or each of the network interface controller codes may have a size of 65536 bits. In certain embodiments, for example, each of the network interface controller codes may have a size of less than 8192 bits, for example less than 4096 bits, less than 2048 bits, less than 1024 bits, or each of the network interface controller codes may have a size of less than 256 bits.

In certain embodiments, for example, each of the first record and the second record may contain a destination port number associated with the destination application (the first application or the second application). In certain embodiments, for example, the destination port number associated with the destination application may be used to direct packet data from the network security software resident on the destination node (the destination node may be the first node or the second node and the network security software may be the first network security software or the second network security software) to the destination application. In certain embodiments, for example, the destination port number associated with the destination application may be used as an index by the network security software resident on the source node (the source node may be the first node or the second node different from the destination node and the network security software may be the first network security software or the second network security software) to identify the appropriate record in the corresponding first preconfigured list.

In certain embodiments, for example, each of the first record and the second record may contain a destination port number (or an identifier associated with the destination port number) associated with the network security software resident on the destination node (the destination node may be the first node or the second node and the network security software may be the first network security software or the second network security software). In certain embodiments, for example, the destination port number associated with the network security software resident on the destination node may be used by the network security software resident on the source node as a destination address for a network packet. In certain embodiments, for example, the destination port number associated with the network security software resident on the destination node may be used as an endpoint for an encrypted communication pathway (for example an encrypted network tunnel) between the first network security software and the second network security software.

In certain embodiments, for example, each of the first record and the second record may comprise one or plural data description fields (or data description values or data description identifiers). In certain embodiments, for example, one or plural data description fields may designate or be an identifier for a data protocol. In certain embodiments, for example, the data protocol may be a machine-to-machine protocol. In certain embodiments, for example, the data protocol may be an IoT protocol. In certain embodiments, for example, the data protocol may comprise an MQ Telemetry Transport (MQTT) protocol. In certain embodiments, for example, the data protocol may comprise an Advanced Message Queuing Protocol (AMQP). In certain embodiments, for example, the data protocol may comprise a Simple/Streaming Text Oriented Messaging Protocol (STOMP). In certain embodiments, for example, the data protocol may comprise a Data Distribution Service DDS. In certain embodiments, for example, the data protocol may comprise a Constrained Application Protocol (CoAP). In certain embodiments, for example, the data protocol may comprise an Open Platform Communications Unified Architecture (OPC UA) protocol. In certain embodiments, for example, the data protocol may comprise a Java Message Service (JMS) protocol. In certain embodiments, for example, the data protocol may comprise an eXtensible Messaging and Presence Protocol (XMPP). In certain embodiments, for example, the data protocol may comprise a Representational State Transfer (REST) protocol. In certain embodiments, for example, the data protocol may comprise an Open Mobile Alliance Light Weight Machine-to-Machine (OMA LWM2M) protocol. In certain embodiments, for example, the data protocol may comprise a JavaScript Object Notation (JSON) protocol. In certain embodiments, for example, the data protocol may comprise a Simple Network Management Protocol (SNMP). In certain embodiments, for example, the data protocol may comprise a protocol conforming to Technical Report 069: CPE WAN Management Protocol (TR-069—CWMP). In certain embodiments, for example, the data protocol may comprise Hypertext Transfer Protocol (HTTP). In certain embodiments, for example, the data protocol may conform to the Alljoyn framework. In certain embodiments, for example, the data protocol may comprise Modbus protocol (for example Modbus over TCP and UDP). In certain embodiments, for example, the data protocol may conform to VITA 49 radio transport packet specification. In certain embodiments, for example, the data protocol may conform to Edgent protocol. In certain embodiments, for example, the data protocol may comprise a file transfer protocol. In certain embodiments, for example, the data protocol may comprise a domain name server protocol. In certain embodiments, for example, the data protocol may comprise an Internet Control Message Protocol (ICMP). In certain embodiments, for example, the data protocol may comprise a structured query language protocol. In certain embodiments, for example, the data protocol may comprise a publish-subscribe messaging pattern protocol. In certain embodiments, for example, the data protocol may comprise a data distribution service protocol. In certain embodiments, for example, the data protocol may comprise a data structure identifier. In certain embodiments, for example, the data protocol may comprise a data topic. In certain embodiments, for example, the data protocol may comprise a data type (for example “string”, “integer”, “unsigned integer”, “Boolean”, “floating point”, “double precision”, etc.). In certain embodiments, for example, the data protocol may indicate an allowed range (for example a continuous range or a list of allowed values) of values for a data payload. In certain embodiments, for example, the data protocol may comprise a data definition identifier.

In certain embodiments, for example, the one or plural data description fields may comprise a file size or file size identifier (for example a total size of a file being transmitted by one or more payload data). In certain embodiments, for example, the one or plural data description fields may comprise a maximum file size (for example a maximum size of a file being transmitted by one or more payload data). In certain embodiments, for example, the one or plural data description fields may comprise a file name or file name identifier. In certain embodiments, for example, the one or plural data description fields may comprise a command syntax, command type, and/or command type identifier. In certain embodiments, for example, the command type may comprise a SQL command and/or statement, for example the command type may comprise SQLread, SQLwrite, AND/OR, ALTER TABLE, AS (alias), BETWEEN, CREATE DATABASE, CREATE TABLE, CREATE INDEX, CREATE VIEW, DELETE, DROP DATABASE, DROP INDEX, DROP TABLE, EXISTS, GROUP BY, HAVING, IN, INSERT INTO, INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL JOIN, LIKE, ORDER BY, SELECT, SELECT *, SELECT DISTINCT, SELECT INTO, SELECT TOP, TRUNCATE TABLE, UNION, UNION ALL, UPDATE, WHERE, or a combination of two or more of the foregoing commands. In certain embodiments, for example, the command type may comprise a DNS command, for example the command type may comprise IPCONFIG, TRACE ROUTE, NETSTAT, ARP, ROUTE, HOSTNAME, CONTROL NETCONNECTIONS, or a combination of two or more of the foregoing commands. In certain embodiments, for example, the command type may comprise an FTP command, for example the command type may comprise !, $, ?, ACCOUNT, APPEND, ASCII, BEEP, BINARY, BYE, CASE, CD, CDUP, CHMOD, CLOSE, CR, DEBUG, DELETE, DIR, DISCONNECT, EXIT, FORM, GET, GLOB, HASH, HELP, IDLE, IMAGE, IPANY, IPV4, IPV6, LCD, LS, MACDEF, MDELETE, MDIR, MGET, MKDIR, MLS, MODE, MODTIME, MPUT, NEWER, NLIST, NMAP, NTRANS, OPEN, PASSIVE, PROMPT, PROXY, PUT, PWD, QC, QUIT, QUOTE, RECV, REGET, RENAME, RESET, RESTART, RHELP, RMDIR, RSTATUS, RUNIQUE, SEND, SENDPORT, SITE, SIZE, STATUS, STRUCT, SUNIQUE, SYSTEM, TENEX, TICK, TRACE, TYPE, UMASK, USER, VERBOSE, or a combination of two or more of the foregoing commands. In certain embodiments, for example, the command type may comprise a Telnet, an Rlogin, an Rsh, or a Secure Shell command. In certain embodiments, for example, the command type may comprise an ICMP command, for example the command type may comprise PING, TRACEROUTE, ICMP PERMIT, ICMP DENY, or a combination of two or more of the foregoing commands. In certain embodiments, for example, the command type may comprise an MQTT command. In certain embodiments, for example, the one or plural data description fields may comprise a date/time (for example a transmission date/time or a deadline). In certain embodiments, for example, the one or plural data description fields may comprise a time-to-live of the payload data. In certain embodiments, for example, the one or plural data description fields may have a size of at least 64 bits, for example at least 128 bits, at least 256 bits, at least 512 bits, at least 1024 bits, at least 2048 bits, at least 4096 bits, at least 8192 bits, at least 16384 bits, at least 32768 bits, or the one or plural data description fields may have a size of at least 65536 bits. In certain embodiments, for example, the one or plural data description fields may have a size of less than 8192 bits, for example less than 4096 bits, less than 2048 bits, less than 1024 bits, or the one or plural data description fields may have a size of less than 256 bits. In certain embodiments, for example, one or plural data type descriptors present in a data packet may be compared with the one or plural data fields to at least partially determine whether the destination application is authorized to receive data from the data packet.

In certain embodiments, for example, each of the first record and the second record may comprise a private key (or a cryptographic parameter or primitive) for establishing the encrypted communication pathway (for example an encrypted network tunnel), for example by cryptographic key exchange as described herein.

In certain embodiments, for example, a first application being used by a first user and executing on the first node may attempt to establish a listening first port on the first node (for example the first application may open a port and attempt to bind the port to a physical or virtual interface). In certain embodiments, for example, the attempt to establish the listening port may conform to a UDP or a TCP connection protocol. In certain embodiments, for example, the attempt to establish the listening port may conform to a network security protocol, for example an SSL or TLS protocol for a UDP or TCP connection. In certain embodiments, for example, the first network security software (or middleware) may detect the attempt and, in response, the first network security software may form a first network security software listening first port. In certain embodiments, for example, the first network security software listening first port may form a connection with a remote host to become a secure connection endpoint, and data to or from the first application may be transmitted through the secure connection endpoint. In certain embodiments, for example, the first network security software may detect the attempt and allow the first application to establish the listening port, followed by the first network security software forming a connection between a port of the first network security software and the listening port. In certain embodiments, for example, the first network security software may be present on the first node, processor, or computing device. In certain embodiments, for example, the first network security software may comprise a network stack application programming interface function called by the first application. In certain embodiments, for example, the network stack application programming interface function may be, for example, a bind function. In certain embodiments, for example, the network stack application programming interface function may be a listen function. In certain embodiments, for example, the first network security software may be present on the second node, processor, or computing device. In certain embodiments, for example, the first network security software may be present on a third node of the plural nodes. In certain embodiments, for example, the first network security software may detect the attempt and prevent the first port from binding to the physical interface. In certain embodiments, for example, the first network security software may redirect the first application to establish a listening port on the loopback interface, followed by the first network security software forming a connection by the loopback interface with the first application. In certain embodiments, for example, the first network security software may prevent the first application from binding the first port to any interface. In certain embodiments, for example, the first network security software may form a connection (for example a direct connection) with the first application without using the loopback interface. In certain embodiments, for example, the first network security software may form a connection (for example a direct connection) with the first application only after at least one other connection is established (for example a connection between the first network security software and the second network security software, such as a connection between the first network security software and the second network security software dedicated to transmitting data having a specified protocol between the first application and the second application).

In certain embodiments, for example, prior to forming the connection with the first application software or opening the dedicated listening port, the first network security middleware may inspect the first application and the first user making the request to open a listening port. In certain embodiments, for example, the first network security software may obtain one or plural parameters (for example process parameters) for inspection and validate the one or plural parameters against a first preconfigured list (for example a list having the format of a preconfigured list as described herein) prior to allowing the combination of the first user and the first application to transmit or receive data (for example to transmit or to receive data according to a network protocol). In certain embodiments, for example, the one or plural parameters may comprise identifiers for the first user and the first application, and these parameters may be compared with a list of allowed 2-tuple values present in the first preconfigured list (for example in a record of the first preconfigured list). If the 2-tuple is not present in the first preconfigured list, for example, the first network security software may prevent the combination of the first application and the first user from receiving or transmitting data. In certain embodiments, for example, the one or plural parameters may comprise identifiers for the first user, the first application, and the requested port number (i.e., the port number associated with the listening port), and these parameters may be compared with a list of allowed 3-tuple values present in the first preconfigured list. In certain embodiments, for example, the identifiers for the first user, the first application, and the requested port number may correspond to a user of a destination application, the destination application, and a destination port number in a record of the first preconfigured list. If the 3-tuple is not present in the first preconfigured list, for example, the first network security software may prevent the combination of the first application and the first user from receiving or transmitting data.

In certain embodiments, for example, a second application being used by a second user and executing on the second node may attempt to form a connection with the combination of the first application and the first user over the listening first port (for example by attempting to send a connection request through a network stack of the second node). In certain embodiments, for example, the attempt to establish the connection may conform to a UDP or a TCP connection protocol. In certain embodiments, for example, the attempt to establish the connection may conform to a network security protocol, for example an SSL or TLS protocol for a UDP or TCP connection. In certain embodiments, for example, in response to detecting the attempt to establish a connection, a second network security software may form a connection with the first network security software listening first port for the purpose of transmitting data to and/or from the second application from and/or to the first application via the first network security program. In certain embodiments, for example, the second network security software may detect the second application attempt and allow the second application to connect to the second network security software, followed by the second network security software forming a connection with the first network security software. In certain embodiments, for example, the second network security software may be present on the second node, processor, or computing device. In certain embodiments, for example, the second network security software may comprise a network stack application programming interface function called by the second application. In certain embodiments, for example, the network stack application programming interface function may be a bind function (for example bind( )). In certain embodiments, for example, the network stack application programming interface function may be, for example, a connect function (for example connect( )). In certain embodiments, for example, the network stack application programming interface function may be, for example, a function which puts a software port into a listening state (for example listen( )). In certain embodiments, for example, the network stack application programming interface function may be, for example, a close function (for example close( )). In certain embodiments, for example, the second network security software may be present on the first node, processor, or computing device. In certain embodiments, for example, the second network security software may be present on a third node of the plural nodes. In certain embodiments, for example, the second network security software may be the same software as the first network security software (for example the first network security software and the second network security software may be different copies of the computer-readable program code (for example copies obtained from different copies of the at least one component)). In certain embodiments, for example, the second network security software may detect the second application attempt and prevent a port associated with the combination of the second application and the second user (the “second port”) from binding or connecting to a physical interface. In certain embodiments, for example, the second network security software may redirect the second application to connect with the second network security software via a loopback interface. In certain embodiments, for example, the second network security software may prevent the second application from binding or connecting the second port to any physical interface. In certain embodiments, for example, the second network security software may form a connection (for example a direct connection) with the second application without use of a loopback interface. In certain embodiments, for example, the second network security software may communicate with the second application by kernel read and/or write commands. In certain embodiments, for example, the first network security software may form a connection (for example a direct connection) with the first application only after at least one other connection is established (for example a connection between the first network security software and the second network security software, such as a connection between the first network security software and the second network security software dedicated to transmitting data having a specified protocol between the first application and the second application).

In certain embodiments, for example, prior to forming the connection with the second application or forming a connection with the first network security software, the second network security software may inspect a combination of the second application and the second user. In certain embodiments, for example, the second network security software may obtain one or plural parameters for the inspection and validate the one or plural parameters against a second preconfigured list prior to allowing the combination of the second user and the second application to transmit or receive data. In certain embodiments, for example, the one or plural parameters may comprise identifiers for the second user and the second application, and these parameters may be compared with a list of allowed 2-tuple values present in the second preconfigured list. If the 2-tuple is not present in the second preconfigured list, for example, the second network security software may prevent the combination of the second application and the second user from receiving or transmitting data. In certain embodiments, for example, the one or plural parameters may comprise identifiers for the second user, the second application, and a destination port number for the requested connection (for example a destination port number associated with the first application), and these parameters may be compared with a list of allowed 3-tuple values present in the second preconfigured list. In certain embodiments, for example, the second user, the second application, and a destination port number for the requested connection may correspond to a user of a source application, the source application, and a port number associated with the destination application present in a record of the second preconfigured list. If the 3-tuple is not present in the second preconfigured list, for example, the second network security software may prevent the combination of the second application and the second user from receiving or transmitting data.

In certain embodiments, for example, the second network security software may use at least the aforementioned destination port number or a destination port identifier (and also optionally an identifier for the source application, an identifier for a user of the source application, or a combination of the identifier for the source application and the identifier for the user of the source application) to identify a different destination port number corresponding to a listening port of the first network security software. In certain embodiments, for example, the second network security software may use at least the aforementioned destination port number or destination port identifier (and also optionally an identifier for the source application, an identifier for a user of the source application, or a combination of the identifier for the source application and the identifier for the user of the source application) for the requested connection as an index into the second preconfigured list to identify a record containing the port number for the listening port of the first network security software. In certain embodiments, for example, said port number for the listening port may be stored in the second preconfigured list.

In certain embodiments, for example, the second network security software may construct or assemble, as described herein, a connection request packet comprising a packet header and metadata. In certain embodiments, for example, the packet header may comprise a destination network address specified by the connection request of the second application. In certain embodiments, for example, the packet header may comprise a destination network address obtainable from (for example specified by or computable from) the second configuration file (for example the destination network address may be specified by or computable from the record identified by at least the destination port number associated with the first application). In certain embodiments, for example, the packet header may comprise destination port number corresponding to the listening port established by the first network security software. In certain embodiments, for example, the packet header may comprise a source network address specified by the connection request of the second application. In certain embodiments, for example, the packet header may comprise a source network address obtainable from (for example specified by or computable from) the second configuration file (for example specified by or computable from the record identified by at least the destination port number associated with the first application). In certain embodiments, for example, the packet header may comprise a source port number associated with the second network security software that has been dynamically assigned (for example by a kernel of the second node). In certain embodiments, for example, the packet header may comprise a non-ephemeral source port number associated with the second network security software, wherein the non-ephemeral source port number is obtained from the second preconfigured list (for example the non-ephemeral source port number is specified in the record identified by at least the destination port number associated with the first application). In certain embodiments, for example, the metadata may comprise a packet type indicator. In certain embodiments, for example, the connection request packet may comprise cipher suite parameters according to a security protocol (for example security protocol such as SSL or TLS).

In certain embodiments, for example, first network security software may drop (or quarantine) the connection request packet if the packet type indicator does not correspond to an expected connection request packet type indicator. In certain embodiments, for example, in response to a threshold number of dropped or rejected connection requests (for example in response to a threshold number of dropped or rejected connection request packets received) from a node (for example connection requests from the second node or another of the plural nodes or a node not present in the plural nodes) the first network security software may add the node to a blacklist. In certain embodiments, for example, the threshold number may be less than 30 connection requests, for example less than 20, less than 15, less than 10, less than 5, less than 4, less than 3, or the threshold number may be less than 2 dropped or rejected connection requests. In certain embodiments, for example, the threshold number may be in the range of 2-10 connection requests, for example in the range of 2-8, in the range of 2-5, or the threshold number may be in the range of 2-4 connection requests. In certain embodiments, for example, the first network security software may drop (for example without attempting to verify) any further connection requests from the sending port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the first network security software may drop (for example without attempting to verify) any further connection requests from any port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the first network security software may terminate all connections (for example inclusive of network tunnels) with the blacklisted node, processor, or computing device. In certain embodiments, for example, the first network security software may drop (for example without attempting to verify) any further connection requests from the sending port after 2 dropped or rejected connection requests, and the network security software may terminate all connections (for example inclusive of network tunnels) after 10 dropped or rejected connection requests.

In certain embodiments, for example, the first network security software and the second network security software may negotiate an encrypted communication pathway (for example an encrypted network tunnel) according to an agreed-to cipher suite, the negotiating based at least on a first private key present in the first preconfigured list and a second private key present in a second preconfigured list. In certain embodiments, for example, the agreed-to choice of cipher suite may be preconfigured. In certain embodiments, for example, the agreed-to choice of cipher suite may be mandatory (i.e., the first node may not select an alternative cipher suite in a connection request reply packet). In certain embodiments, for example, the first private key and the second private key may be different. In certain embodiments, for example, the first private key and the second private key may be the same. In certain embodiments, for example, the first network security software and the second network security software may each execute a key exchange algorithm to generate a symmetric encryption key for encryption of metadata and optionally for encryption of payload data present in network packets transmitted through the negotiated encrypted communication pathway. In certain embodiments, for example, rather than negotiating an encrypted communication pathway, metadata may be protected by passing the metadata through a hash function to form hashed metadata for inclusion in a network packet for transmission over a communication pathway extending between the first network security software and the second network security software. In certain further embodiments, for example, the metadata may be combined with a random number and passed through a hash function to form a salted hashed metadata prior to insertion by the second network security software into a network packet. In certain embodiments, for example, the first network security software may know the hash function used (and, if used, the random number) in order to verify the contents of the metadata.

In certain embodiments, for example, following negotiation of the encrypted communication pathway, the first network security software may construct a first node authentication and authorization packet having the structure of a node authentication and authorization packet as described herein, and transmit the first node authentication and authorization packet to the second node, processor, or computing device. In certain embodiments, for example, the first network security software may obtain a first node authentication code for inclusion in metadata of the first node authentication and authorization packet from a first record of the first configuration file, the first record identified at least based the destination port number of the first network security software. In certain embodiments, for example, upon receipt of the first node authentication and authorization packet, the second network security software may decrypt (or, if applicable, check the hash value of) the first node authentication code and compare the value of the first node authentication code with a value obtained from a second record of the second preconfigured list, the second record identified at least based on the destination port number of the first network security software. In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the first network security software executing in an application space (for example in an application space of the first node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the second network security software executing in an application space (for example in an application space of the second node). In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the first network security software executing in kernel space (for example in a kernel space of the first node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the second network security software executing in a kernel space (for example in a kernel space of the second node).

In certain embodiments, for example, network security software resident on one of the plural nodes may drop (or quarantine) a received node authentication and authorization packet if the value of a node authentication code extracted from the received packet does not match an expected value. In certain embodiments, for example, in response to a threshold number of dropped or rejected node authentication and authorization packets from a different node (for example another one of the plural nodes or a node not one of the plural nodes), the network security software may add the node to a blacklist. In certain embodiments, for example, the threshold number may be less than 30 node authentication and authorization packets, for example less than 20, less than 15, less than 10, less than 5, less than 4, less than 3, or the threshold number may be less than 2 dropped or rejected node authentication and authorization packets. In certain embodiments, for example, the threshold number may be in the range of 2-10 node authentication and authorization packets, for example in the range of 2-8, in the range of 2-5, or the threshold number may be in the range of 2-4 node authentication and authorization packets. In certain embodiments, for example, the network security software may drop (for example without attempting to verify) any further node authentication and authorization packets from the sending port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the network security software may drop (for example without attempting to verify) any further node authentication and authorization packets from any port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the network security software may terminate all connections (for example inclusive of encrypted communication pathways) with the blacklisted node, processor, or computing device. In certain embodiments, for example, the first network security software may drop (for example without attempting to verify) any further node authentication and authorization packets from the sending port after 2 dropped or rejected node authentication and authorization packets, and the network security software may terminate all connections (for example inclusive of encrypted communication pathways) after 10 dropped or rejected node authentication and authorization packets.

In certain embodiments, for example, following negotiation of the encrypted communication pathway the second network security software may construct a second node authentication and authorization packet having the structure of a node authentication and authorization packet as described herein, and transmit the second node authentication and authorization packet to the first node, processor, or computing device. In certain embodiments, for example, the second node authentication and authorization packet may be transmitted prior to the transmission of the first node authentication and authorization packet. In certain embodiments, for example, the second node authentication and authorization packet may be transmitted after the transmission of the first node authentication and authorization packet. In certain embodiments, for example, the second node authentication and authorization packet may be transmitted after the decrypting and comparing the first node authentication and authorization packet. In certain embodiments, for example, the first node authentication and authorization packet may be transmitted after the decrypting and comparing the second node authentication and authorization packet. In certain embodiments, for example, the second node authentication and authorization packet may not be transmitted if the first node authentication and authorization packet is dropped (or quarantined). In certain embodiments, for example, the first node authentication and authorization packet may not be transmitted if the second node authentication and authorization packet is dropped. In certain embodiments, for example, the second network security software may obtain a second node authentication code for inclusion in metadata of the second node authentication and authorization packet from a second record of the second configuration file, the second record identified at least based the destination port number of the second network security software. In certain embodiments, for example, upon receipt of the second node authentication and authorization packet, the first network security software may decrypt (or, if applicable, check the hash value of) the second node authentication code and compare the value of the second node authentication code with a value obtained from a first record of the first preconfigured list, the first record identified at least based on the destination port number of the second network security software. In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the second network security software executing in an application space (for example in an application space of the second node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the first network security software executing in an application space (for example in an application space of the first node). In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the second network security software executing in kernel space (for example in a kernel space of the second node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the first network security software executing in a kernel space (for example in a kernel space of the first node).

In certain embodiments, for example, following negotiation of the encrypted communication pathway the first network security software may construct a first payload data authorization and authentication packet having the structure of a payload data authorization and authentication packet as described herein, and transmit the first payload data authorization and authentication packet to the second node, processor, or computing device. In certain embodiments, for example, the first payload data authorization and authentication packet may be constructed and transmitted following construction and transmission of the first node authentication and authorization packet. In certain embodiments, for example, the first network security software may obtain payload data authorization and authentication parameters for inclusion in metadata of the first payload data authorization and authentication packet from the first record of the first configuration file. In certain embodiments, for example, upon receipt of the first payload data authorization and authentication packet, the second network security software may decrypt (or, if applicable, check the hash value of) the payload data authorization and authentication parameters and compare the values with values obtained from the second record of the second preconfigured list. In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the first network security software executing in an application space (for example in an application space of the first node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the second network security software executing in an application space (for example in an application space of the second node). In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the first network security software executing in kernel space (for example in a kernel space of the first node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the second network security software executing in a kernel space (for example in a kernel space of the second node).

In certain embodiments, for example, network security software resident on one of the plural nodes may drop a received payload data authorization and authentication packet if the value of payload data authorization and authentication parameters extracted from the received packet do not match an expected value. In certain embodiments, for example, in response to a threshold number of dropped or rejected payload data authorization and authentication packets from a different node (for example another one of the plural nodes or a node not one of the plural nodes), the network security software may add the node to a blacklist. In certain embodiments, for example, the threshold number may be less than 30 payload data authorization and authentication packets, for example less than 20, less than 15, less than 10, less than 5, less than 4, less than 3, or the threshold number may be less than 2 dropped or rejected payload data authorization and authentication packets. In certain embodiments, for example, the threshold number may be in the range of 2-10 payload data authorization and authentication packets, for example in the range of 2-8, in the range of 2-5, or the threshold number may be in the range of 2-4 payload data authorization and authentication packets. In certain embodiments, for example, the network security software may drop (for example without attempting to verify) any further payload data authorization and authentication packets from the sending port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the network security software may drop (for example without attempting to verify) any further payload data authorization and authentication packets from any port of the blacklisted node, processor, or computing device. In certain embodiments, for example, the network security software may terminate all connections (for example inclusive of encrypted communication pathways) with the blacklisted node, processor, or computing device. In certain embodiments, for example, the first network security software may drop (for example without attempting to verify) any further node payload data authorization and authentication packets from the sending port after 2 dropped or rejected payload data authorization and authentication packets, and the network security software may terminate all connections (for example inclusive of encrypted communication pathways) after 10 dropped or rejected payload data authorization and authentication packets.

In certain embodiments, for example, following negotiation of the encrypted communication pathway the second network security software may construct a second payload data authorization and authentication packet having the structure of a payload data authorization and authentication packet as described herein, and transmit the second payload data authorization and authentication packet to the first node, processor, or computing device. In certain embodiments, for example, the second payload data authorization and authentication packet may be transmitted prior to transmission of the first payload data authorization and authentication packet. In certain embodiments, for example, the second payload data authorization and authentication packet may be transmitted after transmission of the first payload data authorization and authentication packet. In certain embodiments, for example, the second payload data authorization and authentication packet may be constructed and transmitted following construction and transmission of the second node authentication and authorization packet. In certain embodiments, for example, the second payload data authorization and authentication packet may be transmitted after the decrypting and comparing the first payload data authorization and authentication packet. In certain embodiments, for example, the first payload data authorization and authentication packet may be transmitted after the decrypting and comparing the second payload data authorization and authentication packet. In certain embodiments, for example, the second payload data authorization and authentication packet may not be transmitted if the first payload data authorization and authentication packet is dropped. In certain embodiments, for example, the first payload data authorization and authentication packet may not be transmitted if the second payload data authorization and authentication packet is dropped. In certain embodiments, for example, the second network security software may obtain payload data authorization and authentication parameters for inclusion in metadata of the second payload data authorization and authentication packet from the second record of the second configuration file. In certain embodiments, for example, upon receipt of the second payload data authorization and authentication packet, the first network security software may decrypt (or, if applicable, check the hash value of) the payload data authorization and authentication parameters and compare the values with values obtained from the first record of the first preconfigured list. In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the second network security software, said portion executing in an application space (for example in an application space of the second node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the first network security software, said portion executing in an application space (for example in an application space of the first node). In certain embodiments, for example, the constructing (inclusive of encrypting or forming a hash value for the metadata) and the obtaining may be performed by a portion of the second network security software, said portion executing in kernel space (for example in a kernel space of the second node). In certain embodiments, for example, the decrypting and comparing may be performed by a portion of the first network security software, said portion executing in a kernel space (for example in a kernel space of the first node).

In certain embodiments, for example, if the first node authentication and authorization packet, second node authentication and authorization packet, first payload data authorization and authentication packet, and second payload data authorization and authentication packet are successfully validated, the first application and the second application may transmit payload data packets that the first network security software and the second network security software will allow to be transported across the encrypted communication pathway. In certain embodiments, for example, the destination port number of the first network security software may be recorded in a list of authorized open connections on the first node upon successful validation of the first node authentication and authorization packet, second node authentication and authorization packet, first payload data authorization and authentication packet, and second payload data authorization and authentication packet. In certain embodiments, for example, if any one of the first node authentication and authorization packet, second node authentication and authorization packet, first payload data authorization and authentication packet, and second payload data authorization and authentication packet are not successfully validated, whichever of the first network security software and the second network security software detect the unsuccessful validation may terminate the encrypted communication pathway (and optionally remove the terminated encrypted communication pathway from a list of authorized open connections and/or change the connection status of the encrypted communication pathway). In certain embodiments, for example, terminating the encrypted communication pathway may comprise releasing the destination port. In certain embodiments, for example, in addition to terminating the encrypted communication pathway, the first network security software may terminate the connection formed between the first network security software and the first application. In certain embodiments, for example, in addition to terminating the encrypted communication pathway, the second network security software may terminate the connection formed between the second network security software and the second application.

In certain embodiments, for example, the source port number of the second network security software may be recorded in a list of authorized open connections on the second node upon successful validation of the first node authentication and authorization packet, second node authentication and authorization packet, first payload data authorization and authentication packet, and second payload data authorization and authentication packet. In certain embodiments, for example, a source port number of the second network security software of each payload packet may be compared to the authorized list of open connections on the second node prior to transmitting the payload packet to the first network security software. In certain embodiments, for example, a payload packet may be dropped if said source port does not appear on the authorized list of open connections on the second node, processor, or computing device.

In certain embodiments, for example, a destination port number of each payload packet received by the first network security software may be compared to the authorized list of open connections on the first node, processor, or computing device. In certain embodiments, for example, a payload packet may be dropped if the destination port does not appear in the authorized list of open connections. In certain embodiments, for example, each payload packet received by the first network security software from the network tunnel may be checked to verify that the metadata contains the required second payload data authorization and authentication parameters. In certain embodiments, for example, if said verification fails then the payload packet may be dropped. In certain embodiments, for example, if more than a threshold number of payload packets received by the first network security software from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than 1 payload packet received by the first network security software from the encrypted communication pathway fails to be verified, for example more than 5, more than 10, more than 15, more than 30, more than 50, or if more than 100 payload packets received by the first network security software from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than a threshold number of payload packets received by the first network security software in a continuous sequence from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than 2 payload packets received in a continuous sequence by the first network security software from the encrypted communication pathway fail to be verified, for example more than 4, more than 8, more than 12, more than 18, more than 24, or if more than 48 payload packets received by the first network security software in a continuous sequence from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if a rolling counter defined as (a) a multiplier times (b) the number of payload packets received by the first network security software from the encrypted communication pathway failing to be verified, minus (c) another multiplier times (d) the number of payload packets received by the first network security software from the encrypted communication pathway successfully verified exceeds a threshold number, then the encrypted communication pathway may be terminated. In certain embodiments, for example, the multiplier may be 1 and the another multiplier may be 1. In certain embodiments, for example, the multiplier may be larger than the another multiplier. In certain embodiments, for example, the multiplier may be less than the another multiplier. In certain embodiments, for example, the another multiplier may be 1 and the multiplier may be greater than 1, for example the multiplier may be at least 1.25 (for example 1.25), at least 1.5 (for example 1.5), at least 2 (for example 2), at least 2.5 (for example 2.5), or the multiplier may be at least 3 (for example 3). In certain embodiments, for example, the threshold number may be less than 2, for example less than 4, less than 8, less than 10, less than 20, less than 30, less than 50, or the threshold number may be less than 100. In certain embodiments, for example, the threshold number may be in the range of 10-50, for example in the range of 20-40, or the threshold number may be in the range of 25-35. In certain embodiments, for example, the multiplier may be 1, the another multiplier may be 1, and the threshold number may be less than 30, for example less than 20, or less than 10. In certain embodiments, for example, the multiplier may be 3, the another multiplier may be 1, and the threshold number may be less than 60, for example less than 40, less than 30, less than 20, or less than 10.

In certain embodiments, for example, each payload packet received by the second network security software from the encrypted communication pathway may be checked to verify that the metadata contains the required first payload data authorization and authentication parameters. In certain embodiments, for example, if said verification fails then the payload packet may be dropped. If more than a threshold number of payload packets received by the second network security software from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than 1 payload packet received by the first network security software from the encrypted communication pathway fails to be verified, for example more than 5, more than 10, more than 15, more than 30, more than 50, or if more than 100 payload packets received by the first network security software from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than a threshold number of payload packets received by the second network security software in a continuous sequence from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if more than 2 payload packets received in a continuous sequence by the first network security software from the encrypted communication pathway fail to be verified, for example more than 4, more than 8, more than 12, more than 18, more than 24, or if more than 48 payload packets received by the first network security software in a continuous sequence from the encrypted communication pathway fail to be verified, then the encrypted communication pathway may be terminated. In certain embodiments, for example, if a rolling counter defined as (a) a multiplier times (b) the number of payload packets received by the first network security software from the encrypted communication pathway failing to be verified, minus (c) another multiplier times (d) the number of payload packets received by the first network security software from the encrypted communication pathway successfully verified exceeds a threshold number, then the encrypted communication pathway may be terminated. In certain embodiments, for example, the multiplier may be 1 and the another multiplier may be 1. In certain embodiments, for example, the multiplier may be larger than the another multiplier. In certain embodiments, for example, the multiplier may be less than the another multiplier. In certain embodiments, for example, the another multiplier may be 1 and the multiplier may be greater than 1, for example the multiplier may be at least 1.25 (for example 1.25), at least 1.5 (for example 1.5), at least 2 (for example 2), at least 2.5 (for example 2.5), or the multiplier may be at least 3 (for example 3). In certain embodiments, for example, the threshold number may be less than 2, for example less than 4, less than 8, less than 10, less than 20, less than 30, less than 50, or the threshold number may be less than 100. In certain embodiments, for example, the threshold number may be in the range of 10-50, for example in the range of 20-40, or the threshold number may be in the range of 25-35. In certain embodiments, for example, the multiplier may be 1, the another multiplier may be 1, and the threshold number may be less than 30, for example less than 20, or less than 10. In certain embodiments, for example, the multiplier may be 3, the another multiplier may be 1, and the threshold number may be less than 60, for example less than 40, less than 30, less than 20, or less than 10.

In certain embodiments, for example, the each of the plural nodes may comprise network security software, wherein the network security software may treat any network packet received by a port of the network security software as a malicious packet unless it is a connection request packet, a verified node authentication and authorization packet, a verified payload data authorization and authentication packet, or a verified payload packet as described herein.

In certain embodiments, for example, prior to transmission of a network packet by a first execution thread of the first network security software, a second execution thread (for example of the first network security software) may verify that the user of the first execution thread is an authorized user (for example by determining the user is the root user of a node on which the first execution thread is executing). In certain embodiments, for example, prior to transmission of a network packet by a first execution thread of the second network security, a second execution thread of the second network security software may verify that the user of the first execution thread is an authorized user, for example the root user of a node on which the first execution thread is executing.

In certain embodiments, for example, payload data may be translated by network security software from a native format (for example a native format associated with an application) into a common format prior to insertion in the payload data packet. In certain embodiments, for example, the common format may conform to a machine-to-machine protocol. In certain embodiments, for example, the format may conform to an IoT protocol. In certain embodiments, for example, the common format may conform to an MQ Telemetry Transport (MQTT) protocol. In certain embodiments, for example, the common format may conform to an Advanced Message Queuing Protocol (AMQP). In certain embodiments, for example, the common format may conform to a Simple/Streaming Text Oriented Messaging Protocol (STOMP). In certain embodiments, for example, the common format may conform to a Data Distribution Service DDS. In certain embodiments, for example, the common format may conform to a Constrained Application Protocol (CoAP). In certain embodiments, for example, the common format may conform to a Java Message Service (JMS). In certain embodiments, for example, the common format may conform to an eXtensible Messaging and Presence Protocol (XMPP). In certain embodiments, for example, the common format may conform to a Representational State Transfer (REST) protocol. In certain embodiments, for example, the common format may conform to an Open Mobile Alliance Light Weight Machine-to-Machine (OMA LWM2M) protocol. In certain embodiments, for example, the common format may conform to an Open Platform Communications Unified Architecture (OPC UA) protocol. In certain embodiments, for example, the common format may conform to a JavaScript Object Notation (JSON) protocol. In certain embodiments, for example, the common format may conform to an instant messaging protocol. In certain embodiments, for example, the common format may be a proprietary format (for example may conform to a proprietary protocol). In certain embodiments, for example, the translation may be performed in an application space of node where the network security software is resident. In certain embodiments, for example, network security software may translate received payload data from a common format to a native format according to a receiving application.

In certain embodiments, for example, first network security software resident on a first node may translate data (or a portion thereof) from a first native format to a common format, followed by inclusion of the translated data in a network packet. In certain embodiments, for example, the network packet may be transmitted from the first node to a second node, processor, or computing device. In certain embodiments, for example, second network software resident on the second node may translate the translated data (or translated portion thereof) from the common format into a second native format. In certain embodiments, for example, the data in the second native format may be transmitted to an application resident on the second node, processor, or computing device.

In certain embodiments, for example, prior to the second network security software performing said translating, the second network security software may treat incoming data as translated data and inspect the incoming data based on a predetermined policy (for example a policy based on a data type of the translated data). In certain further embodiments, for example, the inspecting may comprise determining the size(s) (or length(s)) of a portion, portions, or all the incoming data (for example checking using a command such as a rangeCheck command( )), and comparing the determined size(s) with minimum and/or maximum allowed size(s). In certain embodiments, for example, the minimum and/or maximum allowed size(s) may be obtained from the predetermined policy. In certain embodiments, for example, the inspecting may be followed by discarding the incoming data if the data does not conform to the predetermined policy. In certain embodiments, for example, the discarding may be effective to defeat a return-oriented programming exploit. In certain embodiments, for example, the discarding may prevent an attacker from gaining control of a program call stack running on the second node, processor, or computing device.

In certain embodiments, for example, the first native format and the second native format may be the same. In certain embodiments, for example, the first native format and the second native format may be different. In certain embodiments, for example, the translation of the data (or a portion thereof) from the first native format to the common format may chop malware contained in the data (or a portion thereof) into two or more discontiguous segments. In certain embodiments, for example, the translation of the data (or a portion thereof) from the first native format to the common format may render malware contained in the data (or a portion thereof) inoperable. In certain embodiments, for example, the translation of the data (or a portion thereof) from the common format to the second native format may chop (or shred) malware contained in the data (or a portion thereof) into two or more discontiguous segments. In certain embodiments, for example, the translation of the data (or a portion thereof) from the common format to the second native format may not reassemble malware originally contained in the data (or a portion thereof) in its first native format into a contiguous executable code (for example the first native format may be different from the second native format). In certain embodiments, for example, the translation of the data (or a portion thereof) from the common format to the second native format may render malware contained in the data (or a portion thereof) inoperable.

In certain embodiments, for example, the second node of the plural nodes may be a gateway server to different nodes than the plural nodes. In certain embodiments, for example, the second node of the plural nodes may be configured to receive network packet communications by connections which are not negotiated by the second network security software, followed by transmitting at least a portion of the received network packet communications through an authorized encrypted communication pathway that is negotiated by the first network security software and the second network security software. In certain embodiments, for example, the at least a portion of the received network packet communications may be passed through a trusted application to form trusted at least a portion of the received network packet communications, followed by passing the trusted at least a portion of the received network packet communications through the authorized encrypted communication pathway. In certain embodiments, for example, the at least a portion of the received network packet communications may be modified to render any executable computer code present in the received network packet communications nonexecutable. In certain embodiments, for example, the at least a portion of the received network packet communications may be modified, chopped, or shredded to render any executable code present in the received network packet communications nonexecutable. In certain embodiments, for example, the at least a portion of the received network packet communications may be padded to render any executable code present in the received network packet communications nonexecutable. In certain embodiments, for example, the at least a portion of the received network packet communications may be converted to a nonexecutable format. In certain embodiments, for example, the at least a portion of the received network packet communications may be converted to an ASCII text format. In certain embodiments, for example, the at least a portion of the received network packet communications may be passed through a function (for example a bitwise function or a cryptographic function) to render it nonexecutable. In certain embodiments, for example, the ratio of the different nodes to the plural nodes may be less than 1:1, for example less than 1:2, less than 1:3, less than 1:4, less than 1:5, less than 1:8, less than 1:9, less than 1:10, less than 1:20, or the ratio of the different nodes to the plural nodes may be less than 1:50.

Certain embodiments may provide, for example, use of any of the foregoing systems, methods, or apparatuses to defeat an attack over a network (for example an attack by malware resident on the node or on a remote node). In certain embodiments, for example, the attack may comprise a port scan attack whereby the malware detects an open port (for example a port in listening mode) on the node, processor, or computing device.

In certain embodiments, for example, malware may use a compromised password (for example a weak administrator password that has been compromised) to gain access to one or plural nodes, followed by transmitting data from the one or plural nodes.

In certain embodiments, for example, spyware present on a node may transmit keystrokes from a keyboard to a remote machine in order to obtain confidential information (for example a password for the machine or one or plural applications.

In certain embodiments, for example, the attack may comprise the malware spoofing a second node with which the first node is authorized to communicate. In certain embodiments, for example, the malware may monitor network traffic between the node and the further node to determine, for example, a node address, a node port number, a communication session ID, and a network packet sequence number associated with a communication session. In certain further embodiments, for example, the malware may modify Address Resolution Protocol (ARP) caches present on the node and on a router, causing network packets to be routed through the malware. Alternatively, in certain embodiments, for example, the malware may trigger a connection reset between the node and the router. In certain further embodiments, for example, the malware may spoof the node by registering with the router using the determined address and port number, and highjack the communication session with the further node, processor, or computing device. In certain further embodiments, for example, the node may redirect the node traffic to pass through the malware when the node reconnects with the router.

In certain embodiments, for example, the attack may comprise negotiating an encrypted tunnel with a network security agent resident on the node (and, in the case of a man-in-the-middle attack, negotiating a further encrypted tunnel with a second node). In certain embodiments, for example, the malware may obtain one or plural private keys from the node, enabling key exchange between the malware and the node, decryption of encrypted network packets, network packet payloads, and/or network packet metadata. In certain embodiments, for example, the malware may obtain the one or plural private keys based on a flaw in security software. By way of example, certain versions of OpenSSL (publicly available secured socket layer encryption software) contain a bug (the so-called “Heartbleed” bug) that has been exploited malware to read node memory. According to the Heartbleed bug, a malware client may send a “heartbeat” network packet to a server node, the packet containing a payload size parameter. Exploiting the fact that the OpenSSL versions require the server node respond to the heartbeat network packet in kind with the same heartbeat request, the malware may submit a payload size parameter much larger than the actual payload, which may cause the server to send random data from its memory to meet the length requirements of specified by the payload size parameter. By inspecting the random bits of data, in certain instances the malware may be able to identify sufficient cryptographic data to compromise a security protocol.

In certain embodiments, for example, the network attack may comprise a side-channel attack. In certain embodiments, for example, the network attack may comprise a challenge ACK side channel attack. In certain embodiments, for example, the side channel attack may be rendered ineffective by requiring, according to the methods described herein, the exchange and authorization of encrypted device, application, user, and/or data protocol parameters across an encrypted communication pathway prior to authorizing port-to-port communication (or higher than OSI layer three communication) across the encrypted communication pathway and, once port-to-port communication is authorized, further requiring, according to the methods described herein, that each payload passed to an application port is obtained from a network packet containing an expected application, user, and/or data protocol identifier.

In certain embodiments, for example, the network attack may comprise a denial-of-service attack, whereby one or plural remote nodes attempt to temporarily or indefinitely render node resources unavailable to its intended users. In certain embodiments, for example, the denial-of-service attack may comprise a distributed denial of service attack, whereby incoming network packets from plural sources flood the node, processor, or computing device. In certain embodiments, for example, the denial-of-service attack may comprise an OSI application layer attack whereby network packet data may flood application layer memory. In certain further embodiments, for example, the OSI application layer attack may trigger buffer overflow on the node, processor, or computing device. Buffer overflow may result in consumption of all available CPU memory (or in the introduction of malware into an executable region of node memory). In certain embodiments, for example, the denial-of-service attack may comprise a so-called “banana attack” whereby outgoing network packets are redirected to the client, thereby impairing incoming network traffic from reaching the node (and potentially flooding node memory with the redirected network packets). In certain embodiments, for example, the denial-of-service attack may be a so-called “Smurf” attack, whereby malware may spoof the source address of the node in network packets and exploit one or plural misconfigured network devices to cause the network packets to be broadcast to each member of a network. The resulting network traffic may use up the network's bandwidth. In certain embodiments, for example, the denial-of-service attack may comprise the so-called “ping flood”, whereby the node may receive an overwhelming number of ping packets over the network. In the so-called “Ping of death” attack, for example, the malware may provide a malformed ping packet that may consume node resources. In the so-called “BlackNurse attack”, for example, malware may transmit packets indicating that a destination port is unreachable. In certain embodiments, for example, the denial-of-service attack may comprise the so-called “shrew attack”, whereby short synchronized bursts of traffic may disrupt TCP connections on the same link, by exploiting a weakness in TCPs retransmission timeout mechanism. In certain embodiments, for example, the denial-of-service attack may comprise the so-called “Slow Read” attack whereby malware sends properly formed application layer requests but reads responses very slowly, thus trying to exhaust the nodes connection pool. In certain embodiments, for example, the denial-of-service attack may comprise the so-called “teardrop attack”, whereby malformed network fragments with overlapping, oversized payloads are transmitted to the node, processor, or computing device. In certain embodiments, for example, the teardrop attack may compromise certain kernels (for example Windows 3.1x, Windows 95 and Windows NT operating systems, as well as versions of Linux prior to versions 2.0.32 and 2.1.63) due to a bug in their TCP/IP fragmentation re-assembly code. In certain embodiments, for example, the network attack may comprise a malicious file list object (for example a compromised file) configured to be executed by software that is ostensibly not malicious (for example an authorized application software program or an operating system program).

A schematic view of an exemplary data flow for data transmission between a first node 2200 and a second node 2202 across a network 2204 is illustrated in FIG. 22. According to this embodiment, a first application 2206 executing on the first node 2200 and a second application 2208 executing on the second node 2202 attempt to form a communication pathway (or channel) A (the communication pathway (or channel) is shown by the identifier A only for reference, and it is not part of the exemplary data flow managed by network security agent as described below), comprising attempting to associate a first port 2210 of the first application 2206 with a first physical interface 2212 of the first node 2200 and attempting to associate a second port 2214 of the second application 2208 with a second physical interface 2216 of the second node 2202. Of note, the first port 2210 and/or the second port 2214 may have predefined port numbers or may have ephemeral port numbers that are assigned at some point before, during, or subsequent to the attempt to form the communication pathway (or channel) A. According to this embodiment, a first network security agent 2218 and a second network security agent 2220 are cooperatively configured to prevent the attempted communication pathway (or channel) A from being formed. The first network security agent 2218 intercepts the attempt to associate the first port 2210 with the first physical interface 2212 and redirects the first port 2210 to associate with a first loopback interface 2222 of the first node 2200. Furthermore, the first network security agent 2218 causes a third port 2224 of the first network security agent 2218 to associate with the first loopback interface 2222 and a fourth port 2226 of the first network security agent to associate with the first physical interface 2212. The second network security agent 2220 intercepts the attempt to associate the second port 2214 with the second physical interface 2216 and redirects the second port 2214 to associate with a second loopback interface 2228 of the second node 2202. Furthermore, the second network security agent 2220 causes a fifth port 2230 of the second network security agent 2220 to associate with the second loopback interface 2228 and a sixth port 2232 of the second network security agent to associate with the second physical interface 2216. The first application 2206 and the first network security agent 2218 negotiate a first communication pathway (or channel) 2234, the first network security agent 2218 and the second network security agent 2220 negotiate a second communication pathway (or channel) 2236, and the second network security agent 2220 and the second application 2208 negotiate a third communication pathway (or channel) 2238, whereby data may be transmitted by a data path comprising the first communication pathway (or channel) 2234, the second communication pathway (or channel) 2236, and the third communication pathway (or channel) 2238.

A schematic view of an exemplary translated data flow between a first node 2300 and a second node 2302 across a network 2304 is illustrated in FIG. 23. According to this embodiment, a sensor 2306 transmits a sensor reading across a physical interface 2308 of the first node 2300 to sensor software 2310, which may include a driver for the sensor 2306. The sensor software 2310 transmits a first packet 2312 containing the sensor reading in a payload 2314 of the first packet 2312 to a first network security software 2316 via a loopback interface 2318 of the first node 2300 (i.e., the first packet 2312 is passed through a network stack via the loopback interface 2318 and the payload 2314 passed to the first network security software 2316). The first packet payload 2314 has a first native data format A, the first native data format A including an offset, the sensor reading, a fixed-width sensor identifier, and a fixed-width data type identifier. The offset provides an index to the start of the fixed-width sensor identifier in the payload. The sensor reading in the first native data format may be provided in first native units (for example a temperature value may be provided in degrees Celsius, as shown) or may be unitless. The first network security software 2316 includes a translator, the translator configured to convert the sensor data payload 2314 from the first native data format A to a translated format B (to form a translated sensor data payload 2320), the translated format B consisting of the sensor identifier, the data type, and a translated sensor reading, wherein a forward slash (“/”) delimits the sensor identifier and the data type, and a colon (“:”) delimits the data type and the translated sensor data value. The translated sensor reading may be provided in translated units (for example a translated temperature value may be provided in degrees Kelvin, as shown) or may be unitless. The first network security software transmits a second data packet 2322 containing the translated sensor data payload 2320 via a physical interface 2324 across the network 2304 to the second node 2302 via a physical interface 2326 where the second data packet 2322 is received by second network security software 2328. The second network security software 2328 includes a translator, the translator configured to convert the sensor data payload 2320 from the translated format B to a second native data format C expected by a database application, the second native data format C consisting of the sensor identifier, the data type, and a sensor reading in comma delimited format and enclosed in parenthesis. The sensor reading, following conversion from the translated format C by the second network security software 2328, may be provided according to second native units (for example a temperature value may be provided in degrees Fahrenheit, as shown) or may be unitless. The second network security software 2328 transmits a third packet 2330 containing the sensor data payload 2332 having the second native data format C to a database application 2334 via a loopback interface 2336 of the second node 2302.

The network security software (2316 and 2328) may perform additional communication management operations. In addition to translating the payload 2314, the network security software 2316 may be configured to evaluate the payload 2314 prior to the translating to determine whether the payload 2314 conforms to the first native data format A by checking whether the fixed-width sensor identifier is an integer falling within a pre-established valid range, whether the fixed-width data type identifier is one of a pre-established allowed type of data (for example “temp-C”), and whether the sensor reading is an integer or floating point number falling within a pre-established range. If the payload 2314 fails to conform to the first native data format A, the network security software 2316 may discard the payload 2314 without translating it. In addition to translating the payload 2320, the network security software 2328 may be configured to evaluate the payload 2320 prior to the translating to determine whether the payload 2320 conforms to the translated format B by checking whether the sensor identifier is an integer falling within a valid range, whether the data type identifier is one of a pre-established allowed type of data (for example “temp-K”), and whether the sensor reading is an integer or floating point number falling within a pre-established range. If the payload 2320 fails to conform to the translated format B, the network security software 2316 may discard the payload 2320 without translating it.

A schematic view of an exemplary network configuration is illustrated in FIG. 24. The network comprises a first node 2400, a second node 2402, and a third node 2404 exchanging data over network 2406 through a first encrypted bidirectional connection (for example network tunnel) 2408, a second encrypted unidirectional connection (for example network tunnel) 2410, a third encrypted unidirectional connection (for example network tunnel) 2412, a fourth encrypted unidirectional connection (for example network tunnel) 2414, and a fifth encrypted bidirectional connection (for example network tunnel) 2416. The first node 2400 comprises a first application program 2418, a second application program 2420, and a first network security software 2422. The second node 2402 comprises a third application program 2424 and a second network security software 2426. The third node 2404 comprises a fourth application program 2428 and a third network security software 2430. Each of the application programs (2418, 2420, 2424, and 2428) communicate data to and from their respective network security software (2422, 2426, or 2430) by bidirectional connections 2432, 2434, 2436, 2438, 2440, 2442, 2444, 2446, 2448, 2450 as indicated. The first network security software 2422 is configured to (a) transmit data conforming exclusively to a first data protocol received from the first application program 2418 by bidirectional connection 2432 to the first encrypted bidirectional connection (for example network tunnel) 2408; and (b) transmit data conforming exclusively to the first data protocol received from the first encrypted bidirectional connection (for example network tunnel) 2408 to the first application program 2418 by bidirectional connection 2432. The first network security software 2422 is also configured to transmit data conforming exclusively to a second data protocol received from the first application program 2418 by bidirectional connection 2434 to the second encrypted unidirectional connection (for example network tunnel) 2410. The first network security software 2422 is further configured to transmit data conforming exclusively to a third data protocol received from the third encrypted unidirectional connection (for example network tunnel) 2412 to the second application program 2420 by bidirectional connection 2436. The second network security software 2426 is configured to (a) transmit data conforming exclusively to the first data protocol received from the third application program 2424 by bidirectional connection 2438 to the first encrypted bidirectional connection (for example network tunnel) 2408; and (b) transmit data conforming exclusively to the first data protocol received from the first encrypted bidirectional connection (for example network tunnel) 2408 to the third application program 2424 by bidirectional connection 2438. The second network security software 2426 is also configured to transmit data conforming exclusively to a fourth data protocol received from the fourth encrypted unidirectional connection (for example network tunnel) 2414 to the third application program 2424 by bidirectional connection 2440. The second network security software 2426 is further configured to (a) transmit data conforming exclusively to a fifth data protocol received from the third application program 2424 by bidirectional connection 2442 to the fifth encrypted bidirectional connection (for example network tunnel) 2416; and (b) transmit data conforming exclusively to the fifth data protocol received from the fifth encrypted bidirectional connection (for example network tunnel) 2416 to the third application program 2424 by bidirectional connection 2442. The third network security software 2430 is configured to transmit data conforming exclusively to the second data protocol received from the second encrypted unidirectional connection (for example network tunnel) 2410 to the fourth application program 2428 by bidirectional connection 2448. The third network security software 2430 is also configured to transmit data conforming exclusively to the third data protocol received from the fourth application program 2428 by bidirectional connection 2450 to the third encrypted unidirectional connection (for example network tunnel) 2412. The third network security software 2430 is further configured to transmit data conforming exclusively to the fourth data protocol received from the fourth application program 2428 by bidirectional connection 2444 to the fourth encrypted unidirectional connection (for example network tunnel) 2414. The third network security software 2430 is additionally configured to (a) transmit data conforming exclusively to a fifth data protocol received from the fourth application program 2428 by bidirectional connection 2446 to the fifth encrypted bidirectional connection (for example network tunnel) 2416; and (b) transmit data conforming exclusively to the fifth data protocol received from the fifth encrypted bidirectional connection (for example network tunnel) 2416 to the fourth application program 2428 by bidirectional connection 2446.

A schematic view of an exemplary node 2500 transmitting data to a network 2502 is illustrated in FIG. 25. A data packet sent from a program port 2504 by a user 2506 of a program 2508 executing in an application space 2510 to a network stack 2512 is routed to a first driver (or module, for example a kernel loadable module) 2514 of a network security layer 2516 in a kernel space 2518. Based on a list 2520 of allowed network connections (which list is stored in kernel space memory as shown or alternatively stored in application space memory, and at least a portion of the contents of the list may optionally be loaded from an kernel-only readable file or from an application space readable file and optionally passed via an interface to the kernel space 2510), the first driver (or module, for example a kernel loadable module) 2514 verifies that the user 2506 and the program 2508 are permissible, and obtains a network tunnel port number and data protocol for the data packet. The first driver (or module, for example a kernel loadable module) 2514 further verifies that the network tunnel port number is associated with a network tunnel that is in a valid state for transmitting data (for example having an open connection status). A builder module 2522 is invoked to assemble descriptors for the user 2506, the program 2508, and the data protocol into packet metadata. A data portion of the data packet is passed to a translator module 2524 to encode the data into translated data for transmission across the network tunnel. The packet metadata and optionally the translated data are encrypted by an encryption module 2526 using cryptographic keys specific to the network tunnel obtained from a file 2528 and an encrypted result is passed to an assembler module 2530 to form a modified data packet. If the translated data is not encrypted, it may bypass the encryption module 2528 and instead be passed directly to the assembler module 2530 as shown. The modified data packet is communicated to the network stack 2512 and a frame containing the modified data packet transmitted to the network tunnel by a physical interface 2532. Prior to communicating the modified data packet to the network tunnel, the first driver (or module, for example a kernel loadable module) 2514 verifies that the network tunnel is in a valid state for transmitting data. For illustrative purposes only, and not as part of the embodiment, path A shows that data packet sent from the program port 2504 would pass through the network stack 2512 and the physical interface 2532 to the network 2502 were the first driver (or module, for example a kernel loadable module) 2514 not present.

A schematic view of an exemplary node 2600 transmitting data to a network 2602 is illustrated in FIG. 26. A data packet sent from a program port 2604 by a user 2606 of a program 2608 in an application space 2610 to a network stack 2612 is routed to a first driver (or module, for example a kernel loadable module) 2614 of a network security layer 2616 in a kernel space 2618. Based on a list 2620 of allowed network connections (which list is stored in kernel space memory as shown or alternatively stored in application space memory, and at least a portion of the contents of the list may optionally be loaded from an kernel-only readable file or from an application space readable file and optionally passed via an interface to the kernel space 2610), the first driver (or module, for example a kernel loadable module) 2614 verifies that the port 2604 corresponds to a valid port for the user 2606 and the program 2608, and obtains a network tunnel port number and data protocol for the data packet. The first driver (or module, for example a kernel loadable module) 2614 further verifies that the network tunnel port number is associated with a usable network tunnel. A builder module 2622 is invoked to assemble descriptors for the user 2606, the program 2608, and the data protocol into packet metadata. A data portion of the data packet is passed to a translator module 2624 to encode the data into translated data for transmission across the network tunnel. The packet metadata and translated data are encrypted by an encryption module 2626 using cryptographic keys specific to the network tunnel obtained from a file 2628 and an encrypted result is passed to an assembler module 2630 to form a modified data packet. The modified data packet is communicated to the network stack 2612 and a frame containing the modified data packet transmitted to the network tunnel by a physical interface 2632. Prior to communicating the modified data packet to the network tunnel, the first driver (or module, for example a kernel loadable module) 2614 verifies that the network tunnel is in a valid state for transmitting data. The list 2620 of allowed network connections is loaded into kernel access memory by a second driver (or module, for example a kernel loadable module) 2634 having sole permission to read a cryptographically signed, read-only, kernel access-only file 2636 (in an alternative embodiment, the file 2636 may be an application space file and the second driver (or module, for example a kernel loadable module) 2634 may be an application space program). For illustrative purposes only, and not as part of the embodiment, path A shows that data packet sent from the program port 2604 would pass through the network stack 2612 and the physical interface 2632 to the network 2602 were the first driver (or module, for example a kernel loadable module) 2614 not present.

A schematic view of an exemplary node 2600 receiving data from a network 2602 is illustrated in FIG. 27. A data packet containing translated data received from a network tunnel over the network 2602 and sent from a remote program port by a remote user passes through a physical interface 2632 and a network stack 2612. The data packet is received (or intercepted) by a first driver (or module, for example a kernel loadable module) 2614 of a network security layer 2616 in kernel space 2618 and directed to assembler 2630, where it is disassembled into encrypted metadata and the translated data (if the translated data is encrypted the encrypted translated data is passed with the encrypted metadata to an encryption module 2626, otherwise the unencrypted translated data is routed directly to a translation module 2624). Decrypted metadata obtained by passing the encrypted metadata through the encryption module 2626 is inspected by a validation module 2700 to verify that a descriptor comprising a remote application code, a remote user code, and a data protocol code match an expected value for the network tunnel. If the match is verified, the translated data is decrypted (if necessary) by encryption module 2626 and in any event the unencrypted/decrypted translated data is passed to a translator module 2624 for conversion into native format data and transmitted via a loopback interface to a local port 2604 associated with a resident program 2608.

A schematic view of an unsecure node 2800 transmitting data 2802 over a network 2804 to an exemplary secure node 2806 via an exemplary gateway server 2808 is illustrated in FIG. 28. The transmitted data 2802 passes through a physical interface 2810 into a network stack 2812 in a kernel space 2814 of the gateway server 2808 and to a trusted application 2816 in an application space 2818 of the gateway server. Trusted data is transmitted from trusted application 2816 through a loopback interface of the network stack 2812 to a network security software 2820, a portion of which executes in the kernel space 2814 and a portion in a second application space 2818. The network security software 2820 routes the trusted data across the network 2804 through a pre-authorized encrypted network tunnel 2822 to a physical interface 2824 of the secure node 2806. Once in the secure node 2806, the trusted data is passed through a network stack 2826 in a kernel space 2828 of the secure node 2806 and network security software 2830 and directed to a recipient application 2832 in an application space 2834 of the secure node 2806. The network security software 2820 and the network security software 2830 manage data traffic through the encrypted network tunnel 2822 based on parameters (2836 and 2838, respectively) loaded from encrypted, read-only files (2840 and 2842, respectively) by computer programs (2844 and 2846, respectively). The parameters include, inter alia, shared secret node identification codes for the secure node 2806 and the gateway server 2808, a port number of the network security software 2830, a port number of the recipient application 2832, a process identification code and a process owner code associated with the recipient application 2832, and a data protocol associated with the transmitted data 2802. The encrypted, read-only files (2840 and 2842, respectively) are maintained by security configuration server 2848, which transmits updated encrypted configuration data (2850 and 2852, respectively) through encrypted network tunnels (2854 and 2856, respectively) to file update programs (2858 and 2860, respectively) as shown. In another embodiment, the computer programs (2844 and 2846, respectively) responsible for loading the encrypted, read-only files (2840 and 2842, respectively) may be positioned in the application spaces (2818 and 2834, respectively) rather than the kernel spaces (2814 and 2828, respectively).

A schematic view of an unsecure node 2900 transmitting data 2902 over a network 2904 to an exemplary secure node 2906 via an exemplary gateway server 2908 executing a separation kernel 2910 is illustrated in FIG. 29. The transmitted data 2902 passes through a physical interface 2912 into a first network stack 2916 of a first kernel space 2914 and to a trusted application 2918 in a first application space 2920. Trusted data 2922 is transmitted from trusted application 2918 through the separation kernel 2910 to a second network stack 2924 in a second kernel space 2926 and network security software 2928, a portion of which executes in the second kernel space 2926 and a portion in a second application space 2930. The network security software 2928 routes the trusted data 2922 across the network 2904 through a pre-authorized encrypted network tunnel 2932 to a physical interface 2934 of the secure node 2906. Once in the secure node 2906, the trusted data 2922 is passed through a network stack 2936 in a kernel space 2938 of the secure node 2906 and network security software 2940 and directed to a recipient application 2942 in an application space 2944 of the secure node 2906. Network security software 2928 and network security software 2940 manage data traffic through the encrypted network tunnel 2932 based on parameters (2946 and 2948, respectively) loaded from encrypted, read-only files (2950 and 2952, respectively) by kernel mode programs (2954 and 2956, respectively). The encrypted, read-only files (2950 and 2952, respectively) are maintained by security configuration server 2958, which transmits updated encrypted configuration data (2960 and 2962, respectively) through encrypted network tunnels (2964 and 2966, respectively) to file update programs (2968 and 2970, respectively) as shown.

FIG. 34 depicts data processing steps according to an exemplary secure communication protocol. A server security middleware detects 3400 a server bind request by a server application to open a port of the server (the “server port”) and accesses a server lookup table to validate 3402 the authority of the server to open a port having the port number (the “server port number”) assigned to the server port. Following successful validation 3402, the server port is opened and enters 3404 listening mode. A client security middleware detects 3406 a connection request from a client application and accesses a client lookup table to validate 3408 the authority of the client to form a data pathway to the server port. Following successful validation 3408, the client security middleware opens a client port and constructs and transmits 3410 an encrypted tunnel connection request packet 3412, comprising forming client authentication metadata 3414 and inserting the client authentication metadata into the packet 3412, the client authentication metadata comprising a connection state code. The connection state code is configured to be interpreted by the server security middleware that formation of an encrypted tunnel between the client security middleware and the server security middleware is in process. The destination port of the connection request packet 3412 is obtained from the client lookup table based on the server port number, and may be the same or different from the server port number. Upon receipt of the connection request packet 3412 at the server port, the server security middleware inspects 3416 the metadata 3414 and confirms 3416 the connection state. Following the inspecting and confirming 3416, the server security middleware constructs and transmits 3418 an encrypted tunnel reply packet 3420, comprising forming server authentication metadata 3422 and inserting the server authentication metadata into the packet 3420, the server authentication metadata comprising a connection state code. Upon receipt of the reply packet 3420, the client security middleware inspects 3424 the metadata 3422 and confirms 3424 that the connection state code matches an expected connection state (i.e., that formation of an encrypted tunnel between the client security middleware and the server security middleware is in process). Further steps are taken to complete formation of the encrypted tunnel between the client security middleware and the server security middleware, and upon completion both the client security middleware and the server security middleware note that the encrypted tunnel has been formed. Following the comparing and confirming 3424 and formation of the encrypted tunnel, the client security middleware constructs and transmits 3426 a client node identification packet 3428, comprising obtaining a client node identification code from the client lookup table, encrypting the client node identification code and a connection state code, and inserting the encrypted client node identification code 3430 and the encrypted connection state code 3432 (the connection state code indicating that the client and server are authenticating and authorizing one another following establishment of the encrypted network tunnel) into the client node identification packet 3428. Upon receipt of the client node identification packet 3428 at the server, the server security middleware verifies 3434 that the client node identification code is uniquely assigned to the data pathway, comprising successfully decrypting the encrypted client node identification code 3430 and the connection state code 3432 and verifying that the decrypted client node identification code matches an expected value in the server lookup table for the destination port number of the packet. Following the verification 3434, the server security middleware constructs and transmits 3436 a server node identification packet 3438, comprising obtaining a server node identification code from the server lookup table, encrypting the server node identification code and a connection state code (the connection state code indicating that the client and server are authenticating and authorizing data protocol transmitted over the data pathway as well as users and applications that are parties to the data pathway following establishment of the encrypted network tunnel), and inserting the encrypted server node identification code 3440 and the encrypted connection state code 3442 into the server node identification packet 3438. Upon receipt of the server node identification packet 3438 at the client, the client security middleware verifies 3444 that the server node identification code is uniquely assigned to the data pathway, comprising successfully decrypting the encrypted server node identification code 3440 and the connection state code 3442 and verifying that the decrypted server node identification code matches an expected value in the client lookup table. Following the verification 3444, the client security middleware constructs and transmits 3446 a client authorization packet 3448, comprising obtaining client authentication metadata from the client lookup table, encrypting the client authentication metadata and a connection state code, and inserting the encrypted client authentication metadata 3450 and the connection state code 3452 into the client authorization packet 3448, the client authentication metadata comprising a client identifier, a user identifier, and a data protocol descriptor obtained from the client lookup table. Upon receipt of the client authorization packet 3448 at the server, the server security middleware verifies 3454 that the server application is authorized to form a data pathway to receive data from the client application, comprising decrypting the encrypted client authentication metadata 3450 and verifying that the decrypted client authentication metadata matches an expected value in the server lookup table for the data pathway as determined from the server lookup table based on the destination port number of the packet. Following the verification 3454, the server security middleware constructs and transmits 3456 a server authorization packet 3462, comprising obtaining server authentication metadata from the server lookup table, encrypting the server authentication metadata and a connection state code, and inserting the connection state code 3458 and the encrypted server authentication metadata 3460 into the server authorization packet 3462, the server authentication metadata comprising a server identifier, a user identifier, and a data protocol descriptor obtained from the client lookup table. Upon receipt of the server authorization packet 3462 at the client security middleware, the client security middleware verifies 3464 that the client port is authorized to form a data pathway with the server port, comprising decrypting the encrypted server authentication metadata 3460 and verifying that the decrypted server authentication metadata matches an expected value in the server lookup table. Following the verification 3464, the server and the client note that an open connection state exists for transfer of data between the client security middleware and the server security middleware, and the client application transmits data to the client security middleware, and the client security middleware constructs and transmits 3466 a client data packet 3468 to the server, comprising encrypting client authentication metadata and data, and inserting the encrypted client authentication metadata 3470 and encrypted data 3472 into the client data packet 3468. Following receipt of the client data packet 3468 at the server, the server security middleware verifies 3474 that the data is authorized to be received by the server application, comprising successfully decrypting the encrypted client authentication metadata 3470 and verifying that the decrypted client authentication metadata matches an expected value in the server lookup table based on the server port number. Upon verification 3474, the server security middleware transmits 3476 unencrypted data to the server port.

A schematic view of a network configuration first node identifier 3502 and first data structure 3504 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a first node 3500 is depicted and a network configuration second node identifier 3602 and second data structure 3604 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a second node 3600 is depicted in FIGS. 35 & 36. The data structures comprise records 3506 and 3606, each record composed of several fields that are interpreted by network security middleware to define authorized network connections. Optional first fields 3508 and 3608 contain identifiers for a network interface controller(s) of the first node and the second node, respectively. Second fields 3510 and 3610 contain identifiers for application process owners of the first node and the second node, respectively. Third fields 3512 and 3612 contain identifiers for application processes (corresponding to the respective application process owner identifiers) of the first node and the second node, respectively. Fourth fields 3514 and 3614 contain remote node identifiers (for example field 3514 might contain the second node identifier). Fifth fields 3516 and 3616 contain identifiers for remote application process owners. Sixth fields 3518 and 3618 contain identifiers for remote application processes (for example 3516 and 3518 might contain a process owner identifier and an application process identifier for a process on the second node). Optional seventh fields 3520 and 3620 contain port number identifiers for corresponding application processes of the first node and the second node, respectively. As shown, the field may be blank, for example if a local port is dynamically assigned following a connection request. Optional eighth fields 3522 and 3622 contain tunnel port number identifiers for network security software of the first node and network security software of the second node, respectively. As shown, the field may be blank, for example if a local port is dynamically assigned following a connection request. Ninth fields 3524 and 3624 contain port number identifiers for a server application process. The server application process port number identifier may correspond, as the case may be, to either the local application process specified in fields 3510 and 3512 (or 3610 and 3612) on the first node or second node, respectively, or may correspond to a remote application process to which a connection may be formed. Tenth fields 3526 and 3626 contain tunnel port number identifiers for network security software in communication with (and on the same node as) the server application process. The first node 3500 is a source or a destination node for communication of packet data and/or a data stream (and hosts a client or a server) in each of the records present in data structure 3504 (likewise, the second node is a source or a destination node for communication of packet data and/or a data stream in each of the records present in data structure 3604). The first record 3530 of the first node 3500, for example, is used by first network security software on the first node 3500 to configure a connection from the first node (having a node identifier 3502 “SID 1”) to transmit data having data type “0001” from client application process “APP 1” having process owner “USER A” via port “7001” to port “8001” associated with server application process “APP 4” having process owner “USER D” on the second node (having node identifier 3602 “SID2”). Once a connection is formed, the client application process port “7001” is in communication via a loopback interface to first network security software present on the first node 3600, and said first network security software having opened a port “12001” which is bound to interface “NIC 001”. The first network security software has a further connection to port 13001 associated with second network security software on the second node 3600 (having second node identifier 3602 “SID2”). The second network security software at port “12001” is in communication via a loopback interface to process application “APP 4” at port “8001” on the second node 3600. On the second node 3600, the first record 3630 corresponds to the first record 3530 of the first node 3500 because the local process and process owner identifiers (3612 and 3610) match the remote process and process owner identifiers (3518 and 3516) on the first node 3500 and because the destination port fields match (3524 and 3526 match 3624 and 3626, respectively). Records 3532 and 3534 illustrate a scenario in which a common application “APP 2” can be used by two processes (the two processes owned by “USER A” and “USER B”, respectively) on the first node 3500, which are configured to form connections to communicate data with remote processes (application “APP 4” having owner “USER D” on the second node 3600 and “APP 5” having owner “USER F” on a third node (not shown) having an identifier “SID3”). The second record 3632 of the second node 3600 illustrates a scenario in which a process running application “APP 5” having a process owner “USER T” on the second node 3600 is configured to forms a connection to communicate data with a process running application “APP 6” having process owner “USER U” on the third node (not shown).

In addition to the fields 3508-3528 and the fields 3608-3628, in certain embodiments, for example, the data structures 3504 and/or 3604 may contain additional fields. In certain embodiments, for example, the data structure 3504 may be divided among two or more files (for example two files, three files, or four files). In certain embodiments, for example, the data structure 3604 may be divided among two or more files (for example two files, three files, or four files). The ordering of fields 3508-3528 and the ordering of fields 3608-3628 is a non-limiting example comprising certain embodiments of the present disclosure. Certain embodiments may comprise, for example, any of the other orderings which may be generated by permuting the orderings of fields 3508-3528 and/or the orderings of fields 3608-3628, or a subset or all of the orderings which may be generated by permuting the orderings of fields 3508-3528 and/or the orderings of fields 3608-3628.

A schematic view of a network configuration first node identifier 3702 and third data structure 3704 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a first node 3700 is depicted and a network configuration second node identifier 3802 and fourth data structure 3804 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a second node 3800 is depicted in FIGS. 37 & 38. The data structures comprise records 3706 and 3806, each record composed of several fields that are interpreted by network security middleware to define authorized network connections. Optional first fields 3708 and 3808 contain identifiers for a network interface controller(s) of the first node and the second node, respectively. Second fields 3710 and 3810 contain identifiers for application process owners of the first node and the second node, respectively. Third fields 3712 and 3812 contain identifiers for application processes (corresponding to the respective application process owner identifiers) of the first node and the second node, respectively. Fourth fields 3714 and 3814 contain remote node identifiers (for example field 3714 might contain the second node identifier). Fifth fields 3716 and 3816 contain identifiers for remote application process owners. Sixth fields 3718 and 3818 contain identifiers for remote application processes (for example 3716 and 3718 might contain a process owner identifier and an application process identifier for a process on the second node). Optional seventh fields 3720 and 3820 contain port number identifiers for corresponding application processes of the first node and the second node, respectively. As shown, the field may be blank, for example if a local port is dynamically assigned following a connection request. Eighth fields 3724 and 3824 contain port number identifiers for a server application process. The server application process port number identifier may correspond, as the case may be, to either the local application process specified in fields 3710 and 3712 (or 3810 and 3812) on the first node or second node, respectively, or may correspond to a remote application process to which a connection may be formed. The first node 3700 is a source or a destination node for communication of packet data and/or a data stream (and hosts a client or a server) in each of the records present in data structure 3704 (likewise, the second node is a source or a destination node for communication of packet data and/or a data stream in each of the records present in data structure 3804). The first record 3730 of the first node 3700, for example, is used by first network security software on the first node 3700 to configure a connection from the first node (having a node identifier 3702 “SID 1”) to transmit data having data type “0001” from client application process “APP 1” having process owner “USER A” via port “7001” (bound to “NIC 001”) to port “8001” associated with server application process “APP 4” having process owner “USER D” on the second node (having node identifier 3802 “SID2”). Once a connection is formed, packet data from the client application process port “7001” is received by first network security software present on the first node 3800, which performs first network security functions followed by releasing the packet data for transmission to the second node 3800 where it is received by second network security software. The second network security software performs second network security functions and releases the packet to its destination of port “8001” associated with a process running application “APP 4” having process owner “USER D”. On the second node 3800, the first record 3830 corresponds to the first record 3730 of the first node 3700 because the local process and process owner identifiers (3812 and 3810) match the remote process and process owner identifiers (3718 and 3716) on the first node 3700 and because the destination port fields match (3724 matches 3824). Records 3732 and 3734 illustrate a scenario in which a common application “APP 2” can be used by two processes (the two processes owned by “USER A” and “USER B”, respectively) on the first node 3700, which are configured to form connections to communicate data with remote processes (application “APP 4” having owner “USER D” on the second node 3800 and “APP 5” having owner “USER F” on a third node (not shown) having an identifier “SID3”). The second record 3832 of the second node 3800 illustrates a scenario in which a process running application “APP 5” having a process owner “USER T” on the second node 3800 is configured to forms a connection to communicate data with a process running application “APP 6” having process owner “USER U” on the third node (not shown). In addition to the fields 3708-3728 and the fields 3808-3828, in certain embodiments, for example, the data structures 3704 and 3804 may contain additional fields. In certain embodiments, for example, the data structure 3704 may be divided among two or more files (for example two files, three files, or four files). In certain embodiments, for example, the data structure 3804 may be divided among two or more files (for example two files, three files, or four files). The ordering of fields 3708-3728 and the ordering of fields 3808-3828 is a non-limiting example comprising certain embodiments of the present disclosure. Certain embodiments may comprise, for example, any of the other orderings which may be generated by permuting the orderings of fields 3708-3728 and/or the orderings of fields 3808-3828, or a subset or all of the orderings which may be generated by permuting the orderings of fields 3708-3728 and/or the orderings of fields 3808-3828.

A schematic view of a network configuration fifth data structure 3900 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a first node 3902 is depicted and a network configuration sixth data structure 4000 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a second node 3902 is depicted in FIGS. 39 & 40. The data structures comprise records 3904 and 4004, each record composed of several fields 3906 and 4006 that are interpreted by network security middleware to define authorized network connections. First fields 3908 and 4008 contain node identification codes for a source node (i.e., a node having a resident application that is configured to send data to a different application that is resident on a destination node via a network). Second fields 3910 and 4010 contain codes for a network interface controller of the source node, processor, or computing device. Third fields 3912 and 4012 contain unique identifiers for the application configured to send data, the unique identifiers comprising an application code and a user code (for example an application code and a user code obtained from a process status check). Fourth fields 3914 and 4014 contain node identification codes for destination nodes (i.e., nodes having a resident application configured to receive data from an application resident on a source node via a network). Fifth fields 3916 and 4016 contain codes for network interface controllers of the destination node, processor, or computing device. Sixth fields 3918 and 4018 contain unique identifiers for applications configured to receive data, each unique identifier comprising an application code and a user code (for example an application code and a user code obtained from a process status check). Seventh fields 3920 and 4020 contain destination port numbers for the applications configured to receive data. Eighth fields 3922 and 4022 contain port numbers for network security software present on the destination nodes. Ninth fields 3924 and 4024 contain descriptors for authorized data protocol for the connection. The first node is a source or a destination node in each of the records present in data structure 3900 (likewise, the second node is a source or a destination node in each of the records present in data structure 4000). For example, in a first record 3926, the source node identification code is the node identification for the first node (designated “SID(1)”), the source network interface controller code is a code for an interface “2” on the source node (designated “NIC(1,2)”), and the source application identifier names an application “A” resident on the first node and user “T” (designated “APP(A,T)”). The first record 3926 defines a connection for transmitting data having an authorized data protocol descriptor “0001” from application “A” having user “T” on the first node to a destination at the second node, specifically a destination application “B” having a user “U” and a destination port having a port number “7001” via a network tunnel having a port number “12001” (i.e., network security middleware present on the second node will be associated with a port having a port number “12001”, the port forming a destination endpoint of the network tunnel). In order for the connection to form between the first node and the second node, the data structure 4000 must contain an identical entry 4026—otherwise network security middleware present on the first node and/or the second node will prevent formation of the connection. In addition, the source application identifier of each data packet is verified by network security middleware present on the source node and included as metadata in each network packet transmitted over the network tunnel to the destination node, processor, or computing device. Any network packet containing inconsistent application and/or user information will be dropped by network security middleware resident on the destination node before being transmitted to the destination application. In addition, the network security middleware resident on the destination node will terminate the connection if more than a threshold number erroneous packets is detected. A second record 3928 of the first data structure illustrates a case where an application “D” and user “T” resident on the first node are configured to receive data having a protocol descriptor “0002” at an associated port having a port number “8001” via a tunnel port having a port number “13001” (i.e., port number “13001” is associated with or assigned to security middleware resident on the first node) from an application “C” and user “V” resident on a third node (not shown). It is noted that each tunnel port and each destination port are dedicated to a single connection—i.e., the same ports may not be used for different connections even if data is being transmitted between the same applications/users. For example, a third record 3930 (and a matching record 4028 present in the second data structure) differs from the first record only due to a difference in the protocol of the data transmitted, requiring different port numbers as shown.

In addition to the fields 3908-3924 and the fields 4008-4024, in certain embodiments, for example, the data structures 3904 and 4004 may contain additional fields. In certain embodiments, for example, the data structure 3904 may be divided among two or more files (for example two files, three files, or four files). In certain embodiments, for example, the data structure 4004 may be divided among two or more files (for example two files, three files, or four files). The ordering of fields 3908-3924 and the ordering of fields 4008-4024 is a non-limiting example comprising certain embodiments of the present disclosure. Certain embodiments may comprise, for example, any of the other orderings which may be generated by permuting the orderings of fields 3908-3924 and/or the orderings of fields 4008-4024, or a subset or all of the orderings which may be generated by permuting the orderings of fields 3908-3924 and/or the orderings of fields 4008-4024.

A schematic view of a network configuration seventh data structure 4100 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a first node 4102 is depicted and a network configuration eighth data structure 4200 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a second node 4202 is depicted in FIGS. 41 & 42. The data structures comprise records 4104 and 4204, each record composed of several fields 4106 and 4206 that are interpreted by network security middleware to define authorized network connections. First fields 4108 and 4208 contain an identifier for a user of an application. Second fields 4110 and 4210 contains an identifier for the application. Third fields 4112 and 4212 contain a descriptor for an authorized data protocol for the connection. Fourth fields 4114 and 4214 contain a port number for a local application. Fifth fields 4116 and 4216 contain a port number for local network security middleware. Sixth fields 4118 and 4218 contain a port number for a remote application. Seventh fields 4120 and 4220 contain a port number for remote network security middleware. Each record in the seventh data structure 4100 is a unique n-tuple and likewise in the eighth data structure 4200. Furthermore, the fourth field 4114 and the fifth field 4116 of each record in the seventh data structure 4100 form a unique 2-tuple, and likewise in the eighth data structure 4200. In addition, the sixth field 4118 and the seventh field 4118 of each record in the seventh data structure 4100 form a unique 2-tuple, and likewise in the eighth data structure 4200. The first node 4102 and the second node 4202 are constrained by their respective network security middleware to form only those network connections with port numbers and data protocol according to the seventh data structure 4100 and the eighth data structure 4200. For instance, based on the first record 4122 of the seventh data structure 4100 and the first record 4222 of the eighth data structure 4200, “USER A” of “APP 1” may communicate data with “USER D” of “APP 4” between port 6001 associated with “APP 1” and port “11001” associated with “APP 4” because, inter alia, the local application port number 4114 of the first record 4122 of the seventh data structure 4100 matches the remote application port number 4218 of the first record 4222 of the eighth data structure 4200, and vice versa; and because the data protocol descriptor 4112 of the first record 4122 of the seventh data structure 4100 matches the data protocol descriptor 4212 of the first record 4222 of the eighth data structure 4200. However, a “USER B” running application “APP 1” on the first node 4102 would not be able to form a connection based on local port “6002” with “USER D” running “APP 4” at least because the data protocol descriptor 4212 according to second record 4224 of the eighth data structure 4200 (i.e., “V”) differs from the data protocol descriptor 4112 of the second record 4124 of the seventh data structure 4100 (i.e., “W”). Of further note, communication with the same user running the same application but with a different data protocol require different sets of local and remote ports (compare, for example, a third record 4126 and a fourth record 4128 of the seventh data structure 4100). In addition to the fields 4108-4120 and the fields 4208-4220, in certain embodiments, for example, the data structures 4104 and 4204 may contain additional fields. In certain embodiments, for example, the data structure 4104 may be divided among two or more files (for example two files, three files, or four files). In certain embodiments, for example, the data structure 4204 may be divided among two or more files (for example two files, three files, or four files). The ordering of fields 4108-4120 and the ordering of fields 4208-4220 is a non-limiting example comprising certain embodiments of the present disclosure. Certain embodiments may comprise, for example, any of the other orderings which may be generated by permuting the orderings of fields 4108-4120 and/or the orderings of fields 4208-4220, or a subset or all of the orderings which may be generated by permuting the orderings of fields 4108-4120 and/or the orderings of fields 4208-4220.

A schematic view of an exemplary node 4300 transmitting data to a network 4302 is illustrated in FIG. 43. A data packet sent from a program port 4304 by a user 4306 of a program 4308 to a network stack 4312 is routed to a first driver (or module, for example a kernel loadable module) 4314 of a network security layer 4316 (which security layer may operate in a kernel space, an application space, or a combination thereof). Based on a list 4320 of allowed network connections, the first driver (or module, for example a kernel loadable module) 4314 verifies that the user 4306 and the program 4308 are permissible, and obtains a network tunnel port number and data protocol for the data packet. The first driver (or module, for example a kernel loadable module) 4314 further verifies that the network tunnel port number is associated with a network tunnel that is in a valid state for transmitting data (for example having an open connection status). A builder module 4322 is invoked to assemble descriptors for the user 4306, the program 4308, and the data protocol into packet metadata. A data portion of the data packet is passed to a translator module 4324 to encode the data into translated data for transmission across the network tunnel. The packet metadata and optionally the translated data are encrypted by an encryption module 4326 using cryptographic keys specific to the network tunnel obtained from a file 4328 and an encrypted result is passed to an assembler module 4330 to form a modified data packet. If the translated data is not encrypted, it may bypass the encryption module 4328 and instead be passed directly to the assembler module 4330 as shown. The modified data packet is communicated to the network stack 4312 and a frame containing the modified data packet transmitted to the network tunnel by a physical interface 4332. Prior to communicating the modified data packet to the network tunnel, the first driver (or module, for example a kernel loadable module) 4314 verifies that the network tunnel is in a valid state for transmitting data. For illustrative purposes only, and not as part of the embodiment, path A shows that data packet sent from the program port 4304 would pass through the network stack 4312 and the physical interface 4332 to the network 4302 were the first driver (or module, for example a kernel loadable module) 4314 not present.

A schematic view of an exemplary node 4400 receiving data from a network 4402 is illustrated in FIG. 44. A data packet containing translated data received from a network tunnel over the network 4402 and sent from a remote program port by a remote user passes through a physical interface 4432 and a network stack 4412. The data packet is received (or intercepted) by a first driver (or module, for example a kernel loadable module) 4414 (which may optionally be in a kernel space (for example a network API) or an application space) of a network security layer 4416 and directed to assembler 4430, where it is disassembled into encrypted metadata and the translated data (if the translated data is encrypted the encrypted translated data is passed with the encrypted metadata to an encryption module 4426, otherwise the unencrypted translated data is routed directly to a translation module 4424). Decrypted metadata obtained by passing the encrypted metadata through the encryption module 4426 is inspected by a validation module 4401 to verify that a descriptor comprising a remote application code, a remote user code, and a data protocol code match an expected value for the network tunnel. If the match is verified, the translated data is decrypted (if necessary) by encryption module 4426 and in any event the unencrypted/decrypted translated data is passed to a translator module 4424 for conversion into native format data and transmitted via a loopback interface to a local port 4404 associated with a resident program 4408.

A schematic view of an unsecure node 4500 transmitting data 4502 over a network 4504 to an exemplary secure node 4506 via an exemplary gateway server 4508 is illustrated in FIG. 45. The transmitted data 4502 passes through a physical interface 4510 into a network stack 4512 of the gateway server 4508 and to a trusted application 4516 of the gateway server (for example a trusted application running in an application space of the gateway server). Trusted data is transmitted from trusted application 4516 through a loopback interface of the network stack 4512 to a network security software 4520, (in certain embodiments, for example, a portion of the network security software may execute in kernel space and a further portion may execute in application space, or, in certain other embodiments, the network security software may execute only in kernel space or application space). The network security software 4520 routes the trusted data across the network 4504 through a pre-authorized encrypted network tunnel 4522 to a physical interface 4524 of the secure node 4506. Once in the secure node 4506, the trusted data is passed through a network stack 4526 of the secure node 4506 and network security software 4530 and directed to a recipient application 4532 of the secure node 4506. The network security software 4520 and the network security software 4530 manage data traffic through the encrypted network tunnel 4522 based on parameters (4536 and 4538, respectively) loaded from encrypted, read-only files (4540 and 4542, respectively) by computer programs (4544 and 4546, respectively). The parameters include, inter alia, shared secret node identification codes for the secure node 4506 and the gateway server 4508, a port number of the network security software 4530, a port number of the recipient application 4532, a process identification code and a process owner code associated with the recipient application 4532, and a data protocol associated with the transmitted data 4502. The encrypted, read-only files (4540 and 4542, respectively) are maintained by security configuration server 4548, which transmits updated encrypted configuration data (4550 and 4552, respectively) through encrypted network tunnels (4554 and 4556, respectively) to file update programs (4558 and 4560, respectively) as shown. In certain embodiments, for example, the computer programs (4544 and 4546, respectively) responsible for loading the encrypted, read-only files (4540 and 4542, respectively) may be positioned in application spaces. In certain embodiments, for example, the computer programs (4544 and 4546, respectively) responsible for loading the encrypted, read-only files (4540 and 4542, respectively) may be positioned in kernel spaces. In certain embodiments, for example, one the computer programs (4544 or 4546, respectively) responsible for loading the encrypted, read-only files (4540 and 4542, respectively) may be positioned in an application space and the other of the computer programs may be positioned in a kernel space.

A schematic view of a network configuration first node identifier 4602 and ninth data structure 4604 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a first node 4600 is depicted and a network configuration second node identifier 4702 and tenth data structure 4704 stored in a non-transitory computer-readable storage medium (for example a nonvolatile memory) on a second node 4700 is depicted in FIGS. 46 & 47. The data structures comprise records 4606 and 4706, each record composed of several fields that are interpreted by network security middleware to define authorized network connections. First fields 4608 and 4708 contain bind-side port numbers (i.e., numbers for listening ports or ports on server side of a connection) for network connections formed by the first node 4600 and the second node 4700, respectively. Second fields 4610 and 4710 provide a flag, the flag indicating whether an application program will bind (“B”) the port to a loopback interface or form a connection (“C”) with the listening port. Third fields 4612 and 4712 contain port numbers for network security software resident on the first node 4600 and second node 4700, respectively. Fourth fields 4614 and 4714 contain network interface controller identifiers (for example IP addresses, DHCP names, or a proprietary identifiers). Of note, in certain embodiments a network interface controller identifier need not necessarily be specified when the bind/connect flag is set to “B” whereas it must usually be set when the bind/connect flat is set to “C” (i.e., in order for a connect command to have access to a required destination address). Fifth fields 4616 and 4716 contain remote node identifiers. Sixth fields 4618 and 4718 contain a read (“R”), write (“W”) or Read-Write (“R/W”) flag to determine the allowed directionality of data flow. Optional seventh and eighth fields 4620 and 4720 and 4622 and 4722 contain static connection-side application and network security software port numbers (these fields are populated if static port numbers are used on the connect side of a connection, otherwise the optional seventh fields 4620 and 4720 and 4622 and 4722 may be blank and the connect-side ports set ephemerally). Eighth fields 4624 and 4724 contain application information (for example, application identifier and process owner information and a data protocol type) for a local application on the first node 4600 and second node 4700, respectively. Ninth fields 4626 and 4726 contain application information (for example, application identifier and process owner information and a data protocol type) for a remote application.

As shown, a bind-side port number may be associated with either a local application or a remote application. For example, in record 4628, the port number “6001” is associated with an application having the application information specified in column 4624 because the bind/connect flag 4610 is set to “B”. The first node 4600 is a source or a destination node for communication of packet data and/or a data stream (and hosts a client or a server) in each of the records present in data structure 4604 (likewise, the second node is a source or a destination node for communication of packet data and/or a data stream in each of the records present in data structure 4704). The first record 4628 of the first node 4600, for example, is used by network security software on the first node 4600 to do its part to establish a connection from the first node (having a node identifier 4602 “SID 1”) to receive (“R”) data from an application (having an application identifier “RAID 1”) at a local application (having an application identifier “LAID 1”). Once the connection is formed, the application process port “6001” is in communication via a loopback interface to network security software present on the first node 4600, said network security software having opened a port “10001” which is bound to interface “NIC 002” (see record 4728). As record 4630 shows, the network security software on the first node 4600 has a further connection to port “10002” associated with network security software on a third node identified by “SID 3”. Records 4632 and 4732 illustrate a scenario in which the second node 4700 initiates a read-write (“R/W”) connection with the first node 4600 via a network interface controller “NIC 002” on the first node, processor, or computing device. Of note, “LAID 3” in the record 4632 has the same value as “RAID 3” in the record 4732, and “RAID 3” in the record 4632 has the value as “LAID 3” in the record 4732. Of further note, “LAID 3” in the record 4632 refers to a different value than the value “LAID 3” in the record 4732. In addition to the fields 4608-4626 and the fields 4708-4726, in certain embodiments, for example, the data structures 4604 and 4704 may contain additional fields. In certain embodiments, for example, the data structure 4604 may be divided among two or more files (for example two files, three files, or four files). In certain embodiments, for example, the data structure 4704 may be divided among two or more files (for example two files, three files, or four files). The ordering of fields 4608-4626 and the ordering of fields 4708-4726 is a non-limiting example comprising certain embodiments of the present disclosure. Certain embodiments may comprise, for example, any of the other orderings which may be generated by permuting the orderings of fields 4608-4626 and/or the orderings of fields 4708-4726, or a subset or all of the orderings which may be generated by permuting the orderings of fields 4608-4626 and/or the orderings of fields 4708-4726.

Certain embodiments may provide, for example, communication management operations to verify and authorize the provenance (including the source user, source process, source device, and data protocol) of information received in a network packet, and send the verified and authorized information to a distributed ledger ecosystem so that the information may be added to the distributed ledger and referenced in a block added to a blockchain in the ecosystem. The communication management operations may be embedded in a method, system, product, software, middleware, computing infrastructure, apparatus, or a combination of two or more of the foregoing.

Certain embodiments may provide, for example, (a) a first set of communication management operations executable by a first node to verify and authorize the provenance of information, encrypt the information with a private key, send the encrypted information, a public key, and a key rotation index (the public key and the key rotation index associated with the private key) to a distributed ledger ecosystem so that the information, the public key, and the key rotation index may be added to the distributed ledger and referenced in a block added to a blockchain in the ecosystem; and (b) a second set of communication management operations executable by a second node to receive the information, the public key, and the key rotation index from the distributed ledger and to reconstruct the private key to decrypt the information before it is passed to an application.

EXAMPLES Prophetic Example 1

In the following Examples, maximum packet processing rates at several processor loads would be determined for network security middleware consisting of a port filter and metadata processing engine. The port filter would be configured to read the destination port number of each packet and compare said port number to a list of 500 port numbers stored in kernel random access memory. The metadata processing engine would be configured to extract 30 bytes of metadata from a predetermined portion of each packet, optionally decrypt the metadata using a decryption utility executing in application space, and compare said metadata to a list of 500 30-byte data segments stored in kernel random access memory. Each 30 byte metadata would comprise a fixed 10-byte user code, a 10-byte application code, and a 10-byte data protocol code. Results are presented in Table 1.

TABLE 1 Network Security Middleware Performance Packet Processing Rate (sec⁻¹)/ Packet (% wire speed³) Exam- Processor Size No ple Load¹ (bytes) Encrypted² Middleware Middleware 1 2.5 100 No 52,500 56,250 70% 75% 2 2.5 1500 No 60,000 63,750 80% 85% 3 2.5 100 RC4 45,000 — 60% 4 2.5 1500 RC4 52,500 — 70% 5 5 100 No 63,750 67,500 85% 90% 6 5 1500 No 67,500 69,000 90% 92% 7 5 100 RC4 60,000 — 80% 8 5 1500 RC4 63,750 — 85% 9 10 100 No 69,000 69,000 92% 92% 10 10 1500 No 71,250 73,500 95% 98% 11 10 100 RC4 67,500 — 90% 12 10 1500 RC4 69,000 — 92% ¹1 GHz ARM9 processor running Microlinux ²Secure Hash Algorithm 3 ³1 Gb Ethernet interface having 10% packet processing overhead

All publications and patent applications mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication or patent application was specifically and individually indicated to be incorporated by reference.

While preferred embodiments of the present invention have been shown and described herein, it will be obvious to those skilled in the art that such embodiments are provided by way of example only. It is intended that the following claims define the scope of the invention and that methods and structures within the scope of these claims and their equivalents be covered thereby. 

What is claimed is:
 1. A product for authenticating and authorizing provenance of information for one or more information management processes, the product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therein, the computer-readable program code executable on a processor to perform communication management operations, the communication management operations comprising: i) authorizing communication with a computing device on a network, comprising: a) sending a nonpublic first identification code via a communication pathway, the communication pathway pre-established on the network; b) receiving, after sending the nonpublic first identification code, a nonpublic computing device identification code via the pre-established communication pathway; and c) comparing the computing device identification code with a preconfigured value for the computing device, to confirm that the computing device is an authorized computing device on the network; ii) receiving a network packet via the communication pathway, the network packet comprising: (a) information; and (b) an encrypted parameter; iii) verifying that the received information is an authorized communication from a process operating on the authorized computing device, comprising: comparing a decrypted form of the parameter with a preconfigured identifier for the process to confirm that the process is an authorized process; and iv) passing the information to one or more information management processes.
 2. The product of claim 1, wherein the authorizing communication further comprises: a) sending the local program identification code to the computing device via the communication pathway; b) receiving, in response to the sending, a remote application identification code for a remote application program; and c) comparing the remote application identification code with a pre-established value for the remote application program.
 3. The product of claim 2, wherein the further communication management operations comprise: a) sending a data model identification code for the communication pathway to the computing device via the communication pathway; b) receiving, in response to the sending, the data model identification code from the computing device; and c) comparing the received data model identification code with a pre-established value for the communication pathway.
 4. The product of claim 1, wherein the communication management operations further comprise: translating the information to a format expected by the information management process.
 5. The product of claim 4, wherein the information is translated from a pre-established format, the pre-established format determined from a data model identification code for the communication pathway.
 6. The product of claim 1, wherein the communication pathway is encrypted by series of single-use rotated cryptographic keys.
 7. The product of claim 1, wherein at least a portion of the communication management operations are configured to be performed in a processor-accessible kernel space.
 8. The product of claim 1, wherein at least a portion of the communication management operations are configured to be performed in a processor-accessible application space.
 9. The product of claim 1, wherein the communication pathway has a one-to-one correspondence to an n-tuple comprising the local program identification code, the destination port number, and a data model identification code.
 10. The product of claim 1, wherein the communication management operations further comprise: confirming that the computing device has consulted a pre-specified local policy to specifically authorize network packet communication via the communication pathway.
 11. The product of claim 1, wherein the communication management operations further comprise: confirming the information conforms to a data model pre-assigned to the communication pathway.
 12. The product of claim 1, wherein the communication management operations further comprise: confirming the information conforms to a data range pre-assigned to the communication pathway.
 13. The product of claim 1, wherein the communication management operations further comprise: confirming the information conforms to a command type pre-assigned to the communication pathway.
 14. The product of claim 1, wherein the information comprises at least a portion of an executable code.
 15. The product of claim 1, wherein the information comprises at least a portion of a script.
 16. The product of claim 1, wherein the information comprises at least a portion of a transaction.
 17. The product of claim 16, wherein the transaction is configured to modify ownership of at least one token.
 18. The product of claim 16, wherein the transaction is configured to create a smart contract.
 19. The product of claim 16, wherein the transaction is configured to invoke a smart contract method.
 20. The product of claim 16, wherein the transaction is configured to encode data in a file.
 21. The product of claim 1, wherein the information comprises at least a portion of a proposed block of transactions.
 22. The product of claim 1, wherein the information comprises at least a portion of a protocol message.
 23. The product of claim 1, wherein the one or more information management processes comprises a distributed ledger management process.
 24. The product of claim 1, wherein the one or more information management processes comprises a supply chain management process.
 25. The product of claim 1, wherein the one or more information management processes comprises a fintech service.
 26. The product of claim 1, wherein the one or more information management processes comprises a transaction processing service.
 27. The product of claim 1, wherein the one or more information management processes comprises a file update process.
 28. The product of claim 1, wherein the one or more information management processes are distributed on a peer-to-peer network.
 29. The product of claim 1, wherein the remote application program is a wallet on the computing device.
 30. The product of claim 29, wherein the computing device is a mobile device. 